rewrite retest robot comment

[BenTheElder]

1. The Kubernetes project should not have merge-blocking tests that are too flaky to consistently pass, we've worked hard to eliminate these, and if they come up again it should not be treated as normal

2. The text here is way too long, we should focus on the most essentail details. The contributor does not need to know the search query and we're not even including all of it.

3. Prioritize encouraging helping fix test flakes early in the message instead of ~at the end.

4. The full test history link is already included in test failure comments.

follow-up to #35169 (comment)

cc @kubernetes/sig-testing-leads @kubernetes/sig-contributor-experience-leads

[pohly]

/lgtm
/hold

In case you want others to chime in.

[cblecker]

One suggestion, otherwise lgtm

[cblecker]

I'll leave for @Priyankasaggu11929 // @MadhavJivrajani to give the final thumbs up, but this looks great to me!

[Priyankasaggu11929]

/lgtm
/approve

Thanks @BenTheElder and @cblecker!

[BenTheElder]

/assign @upodroid

[upodroid]

LGTM

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: BenTheElder, cblecker, pohly, Priyankasaggu11929, upodroid

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:

• config/jobs/kubernetes/sig-k8s-infra/trusted/OWNERS [upodroid]

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

[BenTheElder]

/hold cancel

[k8s-ci-robot]

@BenTheElder: Updated the job-config configmap in namespace default at cluster test-infra-trusted using the following files:

• key sig-contribex-k8s-triage-robot.yaml using file config/jobs/kubernetes/sig-k8s-infra/trusted/sig-contribex-k8s-triage-robot.yaml
• key sig-contribex-triage-robot-retester.yaml using file config/jobs/kubernetes/sig-k8s-infra/trusted/sig-contribex-triage-robot-retester.yaml

In response to this:

1. The Kubernetes project should not have merge-blocking tests that are too flaky to consistently pass, we've worked hard to eliminate these, and if they come up again it should not be treated as normal

2. The text here is way too long, we should focus on the most essentail details. The contributor does not need to know the search query and we're not even including all of it.

3. Prioritize encouraging helping fix test flakes early in the message instead of ~at the end.

4. The full test history link is already included in test failure comments.

follow-up to #35169 (comment)

cc @kubernetes/sig-testing-leads @kubernetes/sig-contributor-experience-leads

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.