Forward extra authorization query parameters to OAuth and social sources

## What

inject/forward extra authorization query parameters (prompt=, login_hint, idphint) when redirecting to an OAuth/social source. #12607 cites #9971.

## Want

- Inject/forward extra authorization query parameters (prompt=, login_hint, idphint) when redirecting to an OAuth/social source
- #12607 cites #9971

## Ideas this came from

- [#9971 Injecting `prompt=` URL parameters into OAuth source (social login / federated) authorization endpoint request](https://github.com/goauthentik/authentik/issues/9971) — I'm exploring authentik as an alternative to Keycloak for my company's product. We make use of external OIDC sources with which to augment our authentication pr
- [#12607 EH: Modify social/source authentication parameters](https://github.com/goauthentik/authentik/issues/12607) — If I've understood it correctly, when redirecting to an external social/source/fed. provider, all policies along the way are run before the provider is selected
- [#13952 Allow Setting Additional Parameters on OAuth URLs Dynamically](https://github.com/goauthentik/authentik/issues/13952) — I would like to add things like loginhint to the OAuth url dynamically. Like this I could set loginhint to the email of the user currently trying to authenticat
- [#20699 Feature Request: Forward dynamic query parameters (like idphint) from Downstream OIDC Apps to Upstream OIDC Providers](https://github.com/goauthentik/authentik/issues/20699) — Is your feature request related to a problem? Currently, Authentik does not dynamically forward custom query parameters from downstream applications (such as Ju

Start by reading issues #9971, #12607, #13952, and #20699 to compare the requested parameter-forwarding behavior. The issue names no files or tests; done should mean the supported authorization parameters are forwarded when redirecting to OAuth or social sources without changing unrelated parameters.

Written by the indexing model from the issue text.