Don't treat colon as a permission-to-action separator in @PermissionChecker value attribute

[michalvavrik]

• closes: PermissionChecker does not handle list of permission correctly #45224
• intention of this PR is to keep matching between @PermissionsAllowed and @PermissionChecker simple, because : can be used inside claims etc. without having a special meaning (like the permission-to-actions separator); see linked issue
• there was a build-time validation that prevented using the permission-to-action separator in the @PermissionChecker
• agreed behavior:
  • colon used in the @PermissionChecker is just a plain character
  • @PermissionsAllowed and @PermissionChecker values are matched based on a string equality, no actions exist
  • when @PermissionsAllowed attribute inclusive is set to true and read is granted by a permission checker, then all the read:all, read:whatever inside same annotation instance value also require a permission checker; this is important because normally it would be one permission, not 3 checkers and it adds complexity

[github-actions]

🙈 The PR is closed and the preview is expired.

[gsmet]

@sberyozkin could you have a look at this one? Probably something we want for 3.18.

[sberyozkin]

@michalvavrik @gsmet Sure, I was looking through PRs and I found I missed this one, sorry

[sberyozkin]

@michalvavrik Thanks for the fix, I'll let you decide in the next few hours how you'd like to deal with suggestions and then I'll merge, cheers

[quarkus-bot]

Status for workflow Quarkus Documentation CI

This is the status report for running Quarkus Documentation CI on commit 6f52091.

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

[quarkus-bot]

Status for workflow Quarkus CI

This is the status report for running Quarkus CI on commit 6f52091.

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