Allow authentication mechanism selection for a REST endpoint with annotation

[michalvavrik]

closes: #34664

Right now, the only way to combine authentication mechanism is per path using HTTP permission - https://quarkus.io/guides/security-authentication-mechanisms#path-specific-authentication-mechanisms. This PR allows to do same per REST endpoint using annotations. This, combining with RBAC annotations should complement annotation-based approach with same capabilities as configuration-based approach has. And greater, for one path depending on consumed content type etc. can match different endpoints.

[sberyozkin]

Super effort @michalvavrik, thanks for keeping fixing high impact issues 👍 .

Might be worth keeping in a Draft state for a bit of time

[github-actions]

🙈 The PR is closed and the preview is expired.

[michalvavrik]

Super effort @michalvavrik, thanks for keeping fixing high impact issues 👍 .

Thank you Sergey.

Might be worth keeping in a Draft state for a bit of time

• Let's see how CI runs, of course I run every test I added, but I can imagine with this volume of changes I could forget stuff.
• I had issues to build documentation locally, so I can imagine I'll push changes when I can see it build and you find a time to review this => it will take couple of rounds anyway, so people will have time to comment.

Anyway, when we go through ^^^ and folk have time to suggest changes (cc @FroMage :-)), I don't see a reason to keep this in draft. You can see there is lot of file changes, though vast majority are tests. For example I won't touch issue on HTTP permissions runtime migration before this is merged in order to avoid merge conflicts.

[FroMage]

That's a nice feature. Not sure I'll use it, but it seems useful.

[michalvavrik]

As far as failures go, you can see that only thing I changed was one line in documentation and previously we had different failures, so it's flaky.

[sberyozkin]

LGTM, but please update the documentation

[quarkus-bot]

Status for workflow Quarkus Documentation CI

This is the status report for running Quarkus Documentation CI on commit 6745bf6.

✅ 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.

⚠️ There are other workflow runs running, you probably need to wait for their status before merging.

[sberyozkin]

Great work, thanks @michalvavrik

[quarkus-bot]

Status for workflow Quarkus CI

This is the status report for running Quarkus CI on commit 6745bf6.

✅ 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.