Test-infra: Cherrypick lables name not consistant

[spzala]

We have a cherrypick-candidate and cherrypick-approved labels and then there is a cherry-pick-not-approved (i.e. do-not-merge/cherry-pick-not-approved). Notice cherrypick vs cherry-pick. Some inconsistency here and it also makes it hard to search issues/labels related to cherry-pick in a single search.
@spiffxp @cblecker @parispittman - I was looking at some labels in relation to discussion we had in ContribEx meeting today and noticed this. If it makes sense to rename these label(s) for consistency and for better usage, I will create a PR but wanted to run by your thoughts first. I also noticed some general inconsistency in doc at few places with use of "cherry pick" vs "cherry-pick vs "cherrypick" but I'm more concerned about labels.

[stevekuznetsov]

@kubernetes/sig-contributor-experience-bugs
/area prow
/kind bug

[spiffxp]

TBH I'm inclined to not care if it involves adding more code to mungegithub. But I agree we should make them consistent in whatever solution we use to replace the existing cherrypick/cherry-pick/🍒 process.

[nikhita]

But I agree we should make them consistent in whatever solution we use to replace the existing cherrypick/cherry-pick/cherries process.

ref https://github.com/kubernetes/test-infra/pull/9128

[nikhita]

Fixed by https://github.com/kubernetes/test-infra/pull/9128. Closing.

/close