Update sig-node KubeletPSI test focus to include Feature label

[eun2ce]

What type of PR is this?

/kind cleanup

What this PR does / why we need it:

This PR updates the sig-node CI configuration to ensure KubeletPSI feature tests continue to run after the feature label is removed in kubernetes/kubernetes#134303.

The change modifies the pull-kubernetes-node-e2e-containerd-kubelet-psi job to include tests with [Feature:KubeletPSI] label in addition to Summary API tests.

This is a companion change to kubernetes/kubernetes#134303, which removes the redundant feature.KubeletPSI label from the test code and replaces it with framework.WithFeatureGate(features.KubeletPSI).

Which issue(s) this PR is related to:

Companion to kubernetes/kubernetes#134303 (partial fix for kubernetes/kubernetes#134172)

Special notes for your reviewer:

This change ensures that when kubernetes/kubernetes#134303 removes the feature.KubeletPSI label from the test code, the CI pipeline will still run the KubeletPSI feature tests through the dedicated job.

The modification changes the focus pattern from --focus="Summary API" to --focus="Summary API|\[Feature:KubeletPSI\]" to include both Summary API tests and any tests with the KubeletPSI feature label.

Does this PR introduce a user-facing change?

NONE

Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.:

N/A - This is a CI configuration change only.

/cc @SergeyKanzhelev

[k8s-ci-robot]

Welcome @eun2ce!

It looks like this is your first PR to kubernetes/test-infra 🎉. Please refer to our pull request process documentation to help your PR have a smooth ride to approval.

You will be prompted by a bot to use commands during the review process. Do not be afraid to follow the prompts! It is okay to experiment. Here is the bot commands documentation.

You can also check if kubernetes/test-infra has its own contribution guidelines.

You may want to refer to our testing guide if you run into trouble with your tests not passing.

If you are having difficulty getting your pull request seen, please follow the recommended escalation practices. Also, for tips and tricks in the contribution process you may want to read the Kubernetes contributor cheat sheet. We want to make sure your contribution gets all the attention it needs!

Thank you, and welcome to Kubernetes. 😃

[k8s-ci-robot]

Hi @eun2ce. Thanks for your PR.

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

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.

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

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

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

Needs approval from an approver in each of these files:

• config/jobs/kubernetes/sig-node/OWNERS

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

[SergeyKanzhelev]

/assign