RFC 7523: Support refresh token for specified client

[eonie]

Preflight checklist

• [X] I could not find a solution in the existing issues, docs, nor discussions.
• [X] I agree to follow this project's Code of Conduct.
• [X] I have read and am following this repository's Contribution Guidelines.
• [ ] This issue affects my Ory Cloud project.
• [ ] I have joined the Ory Community Slack.
• [ ] I am signed up to the Ory Security Patch Newsletter.

Describe your problem

In some scenarios，i need to get access token without a direct user-approval step at the Hydra server. For example , i want to integrate my existing application for user login and virify access token through Hydra. In the same time, i want to support Github Oauth2 for user who want to use. So, I'm going to use the RFC7523 to get the access token when user passed the Github authentication。 Now the RFC7523 grant type only return bearer access token like this

{
    "access_token": "TIauaolbD9nUdAzLnpsLt9ljrxYhr0IbckRJMcFwkDU.NDGVZNOYD9XylETIi5uC5ZRdHcZGQ8vKM6qCKsDyXCE",
    "expires_in": 3599,
    "scope": "openid offline",
    "token_type": "bearer"
}

After the token expired, user will need to get a new access token.

Describe your ideal solution

Based on the above description，i hope Hydra could return refresh token for client which has grant type refresh_token, and then the application could get a new access token by the refresh_token.

Workarounds or alternatives

None

Version

1.11.10

Additional Context

No response