add backport label to prs

[tac0turtle]

Description

to backport a pr add the label backport-to-v0.41.x
for every release branch, we will need to replace or add an entry.

closes: #XXXX

---

Before we can merge this PR, please make sure that all the following items have been
checked off. If any of the checklist items are not applicable, please leave them but
write a little note why.

• Targeted PR against correct branch (see CONTRIBUTING.md)
• Linked to Github issue with discussion and accepted design OR link to spec that describes this work.
• Code follows the module structure standards.
• Wrote unit and integration tests
• Updated relevant documentation (docs/) or specification (x/<module>/spec/)
• Added relevant godoc comments.
• Added a relevant changelog entry to the Unreleased section in CHANGELOG.md
• Re-reviewed Files changed in the Github PR explorer
• Review Codecov Report in the comment section below once CI passes

[amaury1093]

Suggested change

	- label=backport-to-v0.41.x
	- label=backport/0.41.x (Stargate)

i guess we could just use the existing one, it's used exactly for this purpose (PRs on master that need to be backported)

[alessio]

Can we adopt a different terminology, please? I'm proposing to replace backport with cherry-pick. It's technically more correct (and it's mergify's default terminology too)

[tac0turtle]

oh okay, I see people marking the actual backport PR with that label so didnt think it was for that. Good to know we can use it on the original PR.

Can we adopt a different terminology, please? I'm proposing to replace backport with cherry-pick. It's technically more correct (and it's mergify's default terminology too)

The mergify term is backport. (https://mergify.io/features/backports) Dont have a preference. Feel free to push to this pr with what has consensus

[alessio]

Meh, ok -.- Let's stick to it

[amaury1093]

btw thanks @marbar3778 for having a look at this