test: Resolve ci-check failures in long-running CI tests

[VaniHaripriya]

• Increased the retry count to support long-running tests.
• Added a label check to ensure the ci-check runs only when the needs-ok-to-test label is absent.
• The workflow is triggered when the ok-to-test label is present.

[google-oss-prow]

Hi @VaniHaripriya. Thanks for your PR.

I'm waiting for a kubeflow 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/test-infra repository.

[hbelmiro]

/ok-to-test

[hbelmiro]

@VaniHaripriya since we're adding this validation. The workflows should be triggered also when we add the ok-to-test label.

[hbelmiro]

/lgtm
/unhold

cc @DharmitD

[google-oss-prow]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: hbelmiro

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

The pull request process is described here

Needs approval from an approver in each of these files:

• .github/OWNERS [hbelmiro]

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