Use configured required claims to verify OIDC introspection responses

[sschellh]

Description

When using quarkus-oidc and the bearer access token is opaque/binary and is remotely introspected/verified by the OIDC provider, then the properties in the introspection response are not handled the same ways as the claims in JWT access token.

This results in properties like quarkus.oidc.token.required-claims.realm=value not being honored, if access token is opaque.

Implementation ideas

No response

[quarkus-bot]

/cc @pedroigor (oidc), @radcortez (config), @sberyozkin (oidc)