Backport of ci: Use pattern for CRT release branch config into release/1.12.x

[hc-github-team-consul-core]

Backport

This PR is auto-generated from #13955 to be assessed for backporting due to the inclusion of the label backport/1.12.

WARNING automatic cherry-pick of commits failed. Commits will require human attention.

The below text is copied from the body of the original PR.

---

This adds a release/** pattern to match all of our release branches.

Description

It was recently announced that pattern matching is now supported in CRT configuration for branch names. What this means is that with a pattern for our release branches we will no longer have to update .release/ci.hcl whenever we need to trigger CRT for a new release branch.

Testing & Reproduction steps

This is one of the patterns listed in their examples, so I would imagine it works. We will know once we push a change to the new release/1.13.x branch.

Also, I triggered the workflows for my dev branch (technically eculver/** to express the wildcard case) which can be seen here: https://github.com/hashicorp/consul/pull/13955/checks.

Links

• CRT Newletter: July 15, 2022 - Pattern matching now supported for branch names in ci.hcl!

[hashicorp-cla]

Thank you for your submission! We require that all contributors sign our Contributor License Agreement ("CLA") before we can accept the contribution. Read and sign the agreement

Learn more about why HashiCorp requires a CLA and what the CLA includes

---

1 out of 2 committers have signed the CLA.

• eculver
• temp

---

temp seems not to be a GitHub user.
You need a GitHub account to be able to sign the CLA. If you already have a GitHub account, please add the email address used for this commit to your account.

_{Have you signed the CLA already but the status is still pending? Recheck it.}