v5.0.0 post release chores

[crodriguezvega]

Description

I added also backport tasks for v2.5.x, v3.4.x, v4.2.x and 5.1.x and removed the backport taks for discontinued releases.

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

[damiannolan]

🙏

[colin-axner]

Should we make adding v5 to compatibility tests a post release chore?

[crodriguezvega]

Should we make adding v5 to compatibility tests a post release chore?

Yeah, good idea! @chatton, can you please check if the changes look ok to you?

[chatton]

Thanks for doing these followups @crodriguezvega !

We need to make some changes though for the test matricies, we want to still be able to run them from the release-v5 branch. So rather than updating the existing set, we can create a new set for v6 (make sure the name of the files align as this is important for reading the correct file)

We can have two entries for the workflow now

release-v5.0.x and release-v6.0.x

The new v6 file can run tests against v5.0.0 as well as the previous versions.

All the other changes look good!

[chatton]

@crodriguezvega it might be worth triggering the v6 test suite before you merge to main. You can do this in the UI via

Actions -> Compatibility E2E -> Run Workflow (choose your branch, not main) -> select release-v6.0.x

[chatton]

LGTM! Thanks @crodriguezvega