chore: add concurrency to actions

[DominicGBauer]

Description

Add concurrency to actions to avoid duplicate actions running after new commit.

More info here https://docs.github.com/en/actions/writing-workflows/workflow-syntax-for-github-actions#example-using-concurrency-to-cancel-any-in-progress-job-or-run

[changeset-bot]

⚠️ No Changeset found

Latest commit: 2f1242c

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[rkistner]

Do we actually need this? I typically like seeing the results of older commits, even if I have pushed newer ones shortly afterwards.

[DominicGBauer]

I wouldn't say we need this. Just feels like a waste IMO. Happy to cull it.

[HeinrichvonStein]

Probably out of the scope of this PR, but should we not look at having a common workflow that the other workflows can 'inherit'/use?

[rkistner]

GitHub Actions are pretty cheap to run (apart from the macos ones), I'd prefer to just keep it.