Flow specific OIDC request/response filter support

[sberyozkin]

Description

OIDC request and response filters can be used to customize how Quarkus OIDC communicates with providers.

If the endpoint supports both bearer and code flows, it can be useful to restrict filters to specific flows only given that the flow can impact how filters are implemented

Implementation ideas

No response

[quarkus-bot]

/cc @pedroigor (oidc)

[sberyozkin]

Doing a similar flow specific restrictions for custom tenant resolvers is trickier because an access to the tenant configuration can be required in order to check if the token is provided as a bearer token. Perhaps it can be restrict to the Authorization: Bearer token case. CC @calvernaz