CMP-3803: Add multiple rhcos4 profiles to TestScanSettingBinding

[taimurhafeez]

Update TestScanSettingBinding to test multiple profiles (rhcos4-e8 and rhcos4-moderate) in a single ScanSettingBinding, porting downstream test 37171 functionality to upstream.

To run the test:
make e2e-parallel E2E_GO_TEST_FLAGS="-v -run TestScanSettingBinding"

Expected output:

025/12/10 16:55:30 ComplianceScan ready (DONE)
2025/12/10 16:55:35 ComplianceScan ready (DONE)
2025/12/10 16:55:40 ComplianceScan ready (DONE)
2025/12/10 16:55:40 All scans in ComplianceSuite have finished (generated-suite)
--- PASS: TestScanSettingBinding (217.68s)
PASS

Note: Pull PR-960 before using this PR.

Assisted by: Claude

[openshift-ci-robot]

@taimurhafeez: This pull request references CMP-3803 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.21.0" version, but no target version was set.

Details

In response to this:

Update TestScanSettingBinding to test multiple profiles (rhcos4-e8 and rhcos4-moderate) in a single ScanSettingBinding, porting downstream test 37171 functionality to upstream.

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]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: taimurhafeez
Once this PR has been reviewed and has the lgtm label, please assign mrogers950 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]

Hi @taimurhafeez. Thanks for your PR.

I'm waiting for a github.com member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

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.