Backport of Set concurrency for workflows into release/1.16.x

[hc-github-team-consul-core]

Backport

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

🚨

Warning automatic cherry-pick of commits failed. If the first commit failed,
you will see a blank no-op commit below. If at least one commit succeeded, you
will see the cherry-picked commits up to, not including, the commit where
the merge conflict occurred.

The person who merged in the original PR is:
@curtbushko
This person should manually cherry-pick the original PR into a new backport PR,
and close this one when the manual backport PR is merged in.

merge conflict error: POST https://api.github.com/repos/hashicorp/consul/merges: 409 Merge conflict []

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

---

Description

• This adds concurrency to the bigger workflows that we run.
• These should only work on 'push' style actions (ie pushing a commit or creating a PR).
• Merges to main as pushes are ok as they are done as part of the merge process and not developers pushing commits over and over.
• I've skipped all the smaller workflows because those will need to be cleaned up/merged together soon(tm)
• It will limit 1 workflow run per branch at a time and will cancel current runs of other workflows.

Testing & Reproduction steps

• try doing 2 commits at the same time and the 1st set of workflows should be cancelled.

You can see in the go-tests below how they were cancelled because I pushed a 2nd commit.

https://github.com/hashicorp/consul/actions/runs/5954040559

Links

PR Checklist

• updated test coverage
• external facing docs updated
• appropriate backport labels added
• not a security concern

---

Overview of commits

• 1699574 - 761aea6

[github-team-consul-core-pr-approver]

Auto approved Consul Bot automated PR

[curtbushko]

Already backported manually.