ci: add merge_group tag to all required workflows.

[DimitrisJim]

Description

This adds the merge group tag to the required workflows in order to not stall on merge (by not triggering the required ones).

Do we want to add this for e2e jobs? Or are we happy running e2e's once before adding to merge group?

---

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 the 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 and Go style guide.
• Wrote unit and integration tests.
• Updated relevant documentation (docs/).
• Added relevant godoc comments.
• Provide a conventional commit message to follow the repository standards.
• Include a descriptive changelog entry when appropriate. This may be left to the discretion of the PR reviewers. (e.g. chores should be omitted from changelog)
• Re-reviewed Files changed in the GitHub PR explorer.
• Review SonarCloud Report in the comment section below once CI passes.

[crodriguezvega]

Looking forward to testing this! 🚀

[gjermundgaraba]

Excited to test this!

[damiannolan]

Do we want to add this for e2e jobs? Or are we happy running e2e's once before adding to merge group?

I think running once is fine..?

Can you give a brief description of exactly what merge_group does?

[DimitrisJim]

Can you give a brief description of exactly what merge_group does?

its an event trigger like push, pull_request etc, basic gist as I've understood is github adds these to merge queue, triggers that event and runs tests and then does the merge for you (instead of us competing for it). Next in line gets brought up to speed and cycle goes again.

merging so we can enable them from settings, lmk from chat if you think we should add e2e's or anything else that comes to mind.