Repo: CI runs on main commits are being cancelled if a new commit lands before CI completes #8773
Description
Suggestion
This PR added concurrency config for our actions. This is great for branch (PR) CI runs as it ensures we don't keep CI runs on old commits if a new commit comes in. So if a user spans a bunch of pushes then we'll only have one run per PR.
However the config also applies to main - which is a problem. We rely on the main CI to validate each commit is correct. We also rely on it to publish a canary version per commit.
This has lead us into this state:
We currently have a breakage in the website caused by a semantic merge conflict.
However we have no idea what commit caused the problem because so many commits have had their CI cancelled.
We need to exclude main from this concurrency config.