fix(replacement): correctly apply reject labelSelectors

[saitejabandaru-in]

Fixes #6035

Description:
When using a Replacement with a reject rule that specifies a labelSelector, the filter was unconditionally rejecting targets purely based on their resource ID (GVK/name/namespace) regardless of their labels.

This was caused by the logic being disjointed: the GVK/name/namespace check and the label/annotation check were evaluated separately, effectively OR-ing them instead of AND-ing them together for a single reject rule.

This PR unifies the evaluation logic in applyReplacement so a target is rejected only if it matches both the resource ID criteria AND the label/annotation criteria of a given reject rule.

Testing:
Added TestReplacementTransformerWithRejectLabelSelector to cover this specific scenario, directly mirroring the user's reproduction case.

[kubernetes-prow]

This PR has multiple commits, and the default merge method is: merge.
You can request commits to be squashed using the label: tide/merge-method-squash

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.

[kubernetes-prow]

Invalid commit message issues detected

Invalid commit messages

Keywords which can automatically close issues and hashtag(#) mentions are not allowed.

• d933e29 fix(replacement): correctly apply reject labelSelectors

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.

[kubernetes-prow]

[APPROVALNOTIFIER] This PR is NOT APPROVED

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

[linux-foundation-easycla]

• ❌ The email address for the commit (0fce027, 6455380, d933e29) is not linked to the GitHub account, preventing the EasyCLA check. Consult this Help Article and GitHub Help to resolve. (To view the commit's email address, add .patch at the end of this PR page's URL.) For further assistance with EasyCLA, please visit our EasyCLA portal and chat with our support bot.

[kubernetes-prow]

Hi @saitejabandaru-in. Thanks for your PR.

I'm waiting for a kubernetes-sigs 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.