[WIP]: CNTRLPLANE-2550: Add support for CEL expression claim mappings for username and groups

[ShazaAldawamneh]

• Updated UsernameClaimMapping.Claim to be optional when ExternalOIDCWithUpstreamParity is enabled.
• Added XValidation rule to require claim when PrefixPolicy is 'Prefix'.
• Updated Expression field to be fully gated behind ExternalOIDCWithUpstreamParity.
• Ensures minimal Authentication CRs pass validation and preserve expected claim in tests.
• Aligned PrefixedClaimMapping for groups with same optional/validation behavior.

[openshift-ci-robot]

Pipeline controller notification
This repo is configured to use the pipeline controller. Second-stage tests will be triggered either automatically or after lgtm label is added, depending on the repository configuration. The pipeline controller will automatically detect which contexts are required and will utilize /test Prow commands to trigger the second stage.

For optional jobs, comment /test ? to see a list of all defined jobs. To trigger manually all jobs from second stage use /pipeline required command.

This repository is configured in: LGTM mode

[openshift-ci-robot]

@ShazaAldawamneh: This pull request references CNTRLPLANE-2550 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "4.22.0" version, but no target version was set.

Details

In response to this:

• Updated UsernameClaimMapping.Claim to be optional when ExternalOIDCWithUpstreamParity is enabled.
• Added XValidation rule to require claim when PrefixPolicy is 'Prefix'.
• Updated Expression field to be fully gated behind ExternalOIDCWithUpstreamParity.
• Ensures minimal Authentication CRs pass validation and preserve expected claim in tests.
• Aligned PrefixedClaimMapping for groups with same optional/validation behavior.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

[openshift-ci]

Hello @ShazaAldawamneh! Some important instructions when contributing to openshift/api:
API design plays an important part in the user experience of OpenShift and as such API PRs are subject to a high level of scrutiny to ensure they follow our best practices. If you haven't already done so, please review the OpenShift API Conventions and ensure that your proposed changes are compliant. Following these conventions will help expedite the api review process for your PR.

[openshift-ci]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign joelspeed for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Details

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[openshift-ci]

@ShazaAldawamneh: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
ci/prow/integration	abc8d56	link	true	/test integration
ci/prow/verify-crd-schema	abc8d56	link	true	/test verify-crd-schema
ci/prow/lint	abc8d56	link	true	/test lint

Full PR test history. Your PR dashboard.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

[everettraven]

This has to be moved to the struct level and needs to be feature gated

[everettraven]

This needs to be moved to the struct level and needs to be feature gated.

[everettraven]

Should this instead be added to the TokenClaimMapping type that is inlined above?