JWT dev mode keys: add two build items to customise

[FroMage]

• Allow encrypted JWT tokens
• Allow cold-restart-resistant keys

This allows Renarde to keep working after #44272 got released, because otherwise there's no way to disable these, and both Renarde and Quarkus end up generating keys, but not setting the same properties (Quarkus did not support encrypted JWT) and not the same features (Quarkus did not support cold-restart-resistent JWT keys).

So now I've moved support for this from Renarde to Quarkus, but made both features conditional on build items, this way, non-Renarde users keep the same behaviour, until one day anyone asks for this to be made standard.

I did consider using configuration keys for this, but it would defeat the purpose of this working OOTB for users.

[quarkus-bot]

Status for workflow Quarkus CI

This is the status report for running Quarkus CI on commit 1babd41.

✅ The latest workflow run for the pull request has completed successfully.

It should be safe to merge provided you have a look at the other checks in the summary.

You can consult the Develocity build scans.

[sberyozkin]

I think it looks good with the build items.
@mcruzdev - do you agree ?

[sberyozkin]

@mcruzdev Hi, I'm going to merge, let us know later what you think, when you get a chance. With the build items it should be just fine

[mcruzdev]

@sberyozkin sorry for delay, I simply missed this pull request in my notifications, I loved this approach/PR.