prow, rehearse: improvements to comment

[dhiller]

Problem

The comment currently is not entirely correct. It neglects the recent changes due to the group of people being allowed to rehearse. Also the comment around how to use the plugin should be hidden in a details section, in order to reduce the visible size of the comment.

Proposed solution

Change text2 as described below.

Proposal for text:

<details>

A rehearsal can be triggered for all jobs by commenting either `/rehearse` or `/rehearse all` on this PR.

A rehearsal for a specific PR can be triggered by commenting `/rehearse {job-name}`.

Commenting `/rehearse ?` triggers a comment with a list of jobs that can be rehearsed.

A pull request can be rehearsed if either the user is authorized to rehearse or the pull
request has the `ok-to-rehearse` label.

Authorized users are the group of users that are members of the KubeVirt GitHub 
organization AND either are approvers[1] for all files in the pull request or are
top-level approvers[1] in the `project-infra` project.

[1]: see [OWNERS](https://www.kubernetes.dev/docs/guide/owners/#owners) file definition for reference.

</details>

Example:

A rehearsal can be triggered for all jobs by commenting either /rehearse or /rehearse all on this PR.

A rehearsal for a specific PR can be triggered by commenting /rehearse {job-name}.

Commenting /rehearse ? triggers a comment with a list of jobs that can be rehearsed.

A pull request can be rehearsed if either the user is authorized to rehearse or the pull
request has the ok-to-rehearse label.

Authorized users are the group of users that are members of the KubeVirt GitHub
organization AND either are approvers[1] for all files in the pull request or are
top-level approvers[1] in the project-infra project.

[1]: see OWNERS file definition for reference.

/good-first-issue
/area prow

[kubevirt-bot]

@dhiller:
This request has been marked as suitable for new contributors.

Guidelines

• No Barrier to Entry
• Clear Task
• Solution Explained
• Provides Context
• Identifies Relevant Code
• Gives Examples
• Ready to Test
• Goldilocks priority
• Up-To-Date

For more details on the requirements of such an issue, please see here and ensure that they are met.

If this request no longer meets these requirements, the label can be removed
by commenting with the /remove-good-first-issue command.

In response to this:

Problem

The comment currently is not entirely correct. It neglects the recent changes due to the group of people being allowed to rehearse. Also the comment around how to use the plugin should be hidden in a details section, in order to reduce the visible size of the comment.

Proposed solution

Change text2 as described below.

Proposal for text:

<details>

A rehearsal can be triggered for all jobs by commenting either `/rehearse` or `/rehearse all` on this PR.

A rehearsal for a specific PR can be triggered by commenting `/rehearse {job-name}`.

Commenting `/rehearse ?` triggers a comment with a list of jobs that can be rehearsed.

A pull request can be rehearsed if either the user is authorized to rehearse or the pull
request has the `ok-to-rehearse` label.

Authorized users are the group of users that are members of the KubeVirt GitHub 
organization AND either are approvers[1] for all files in the pull request or are
top-level approvers[1] in the `project-infra` project.

[1]: see [OWNERS](https://www.kubernetes.dev/docs/guide/owners/#owners) file definition for reference.

</details>

Example:

A rehearsal can be triggered for all jobs by commenting either /rehearse or /rehearse all on this PR.

A rehearsal for a specific PR can be triggered by commenting /rehearse {job-name}.

Commenting /rehearse ? triggers a comment with a list of jobs that can be rehearsed.

A pull request can be rehearsed if either the user is authorized to rehearse or the pull
request has the ok-to-rehearse label.

Authorized users are the group of users that are members of the KubeVirt GitHub
organization AND either are approvers[1] for all files in the pull request or are
top-level approvers[1] in the project-infra project.

[1]: see OWNERS file definition for reference.

/good-first-issue
/area prow

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.