Enhance TestSecurity OIDC to support UserInfo and OidcConfigurationMetadata

[sberyozkin]

Fixes #16697

I will follow up asap with addressing #17074

[sberyozkin]

@stuartwdouglas OK, I've reworked this PR and the new annotation idea works great, thanks for suggesting it.
There is no need to throw the exceptions in case no capability is present because the new (optional) annotations are introduced by test-framework/security-jwt (@JwtSecurity) and test-framework/security-oidc (@OidcSecurity). test-framework/security has only been updated to pass all available annotations to TestSecurityAugmentor - this way any new authentication mechanism specific extension can add as many annotations as needed.
@TestSecurity can still be used for simple JWT/OIDC quarkus-smallrye-jwt/quarkus-oidc endpoints.
The only minor issue is that test-framework/security-jwt (@JwtSecurity) and test-framework/security-oidc (@OidcSecurity) have their own @Claim annotation (since testing quarkus-smallrye-jwt is not possible with @OidcSecurity and quarkus-oidc with JwtSecurity) - but I'm not worried about it.
How does it look now ?
Cheers

[sberyozkin]

Or security-jwt/security-oidc can find the needed annotations without security passing Annotation[] directly to TestSecurityAugmentor - I just did not want to duplicate the code for finding the annotations - but that code can be turned into a static utility code and reused