Fix ppc64le integration job names

[varshadeshmane92]

What the pull request does

The pull request corrects the names of the PPC64LE integration release branch jobs that were added in pull request #36067.

The changes are

• Rename wrongly named jobs added in #36067.by removing master from every affected job name.
• Updated integration release branch 1.33, 1.34, and 1.35 jobs to ci-kubernetes-integration-ppc64le-1-XX
• For each of the three jobs the value of testgrid-tab-name has been set equal to the new job name.

No other jobs and no periodic jobs, have been touched.

Verification

• Every job name plus its matching testgrid-tab-name were checked by hand.
• The config forker tool will append the release suffix for version 1.35 as expected.

/cc @RajalakshmiGirish

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: varshadeshmane92
Once this PR has been reviewed and has the lgtm label, please assign prajyot-parab, saschagrunert 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:

• config/jobs/kubernetes/cloud-provider-ibmcloud/OWNERS
• config/jobs/kubernetes/sig-release/OWNERS

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

[k8s-ci-robot]

Hi @varshadeshmane92. 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.

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.