Update KeycloakPolicyEnforcerAuthorizer to init in a PostConstruct method

[sberyozkin]

No description provided.

[quarkus-bot]

Thanks for your pull request!

The title of your pull request does not follow our editorial rules. Could you have a look?

• title should not end up with ellipsis (make sure the title is complete)

This message is automatically generated by a bot.

[sberyozkin]

All the NPE guards are not needed really as this http policy implementation is not registered now if the oidc and policy enforcer configs are disabled - the problem has been is that the authorizer has been registered even if the oidc is disabled but initialized only if it is enabled.

And a minor update to use a synthetic bean

[sberyozkin]

@pedroigor @gastaldi Making this PR now ready for review - it does not have to make it to 1.13.0.Final so please take your time to review

[gastaldi]

LGTM

[sberyozkin]

@gastaldi Thanks, yeah, I recall your earlier comment where I had to check NPE at the policy check time and it just did not look right :-), so indeed, going the bean way should be safer and no NPE checks are needed

[sberyozkin]

Hey @pedroigor I'm happy to go with George's @gastaldi approval since it is a pure structural update which I'm doing in this PR based on the earlier feedback, any concern - let us know please - I'll start with merging this PR as it will cause a conflict for another pending one which I will resolve next