Provide a fluent API to set up path-specific authorization programmatically

[michalvavrik]

• allow to configure path-specific authorization in code instead of in application.properties
• this PR covers portion of Provide a fluent API to set up Quarkus Security #16728
• more will follow in separate smaller PRs for other configuration (like form auth config, inclusive auth and so on), the specifics needs to be discussed first

[github-actions]

🙈 The PR is closed and the preview is expired.

[sberyozkin]

I suggest to set to Draft as I'm trying to find time to comment on a few things at a time, it looks very good, but it might require a few minor consecutive updates to finalize

[michalvavrik]

I suggest to set to Draft as I'm trying to find time to comment on a few things at a time, it looks very good, but it might require a few minor consecutive updates to finalize

Ok.

[sberyozkin]

@cescoffier FYI, looks good and is part of the effort by @michalvavrik to support fluent API for various parts of Quarkus security

[sberyozkin]

@michalvavrik I can merge sometime tomorrow, just would like to give @cescoffier some heads up, as some interesting follow ups for TLS registry might be imagined, etc

[michalvavrik]

I am quite sure that Failing: extensions/smallrye-openapi/deployment only on Windows is not related, but I'll rebase on current main just for a case.

[quarkus-bot]

Status for workflow Quarkus Documentation CI

This is the status report for running Quarkus Documentation CI on commit 89b0163.

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

Warning

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

[michalvavrik]

I saw the same failures here #48560, hence they are unrelated.