Use concurrency to cancel existing workflow jobs

[andreas-el]

Using concurrency groups to avoid unwanted congestion on subsequent commits.
Also set timeouts to 60 minutes where no timeout was provided.

• PR title captures the intent of the changes, and is fitting for release notes.
• Added appropriate release note label
• Commit history is consistent and clean, in line with the contribution guidelines.
• Make sure tests pass locally (after every commit!)

When applicable

• When there are user facing changes: Updated documentation
• New behavior or changes to existing untested code: Ensured that unit tests are added (See Ground Rules).
• Large PR: Prepare changes in small commits for more convenient review
• Bug fix: Add regression test for the bug
• Bug fix: Create Backport PR to latest release

[larsevj]

This looks good to me.

[larsevj]

I see, these are already covered by the workflows they are called from. 👍

[larsevj]

I believe this is redundant as this only triggers on push to main.

[andreas-el]

Agreed, we don't need this. I've checked the others too. 👍

[codecov-commenter]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 85.26%. Comparing base (06da87b) to head (21d8ae3).
Report is 3 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #7375      +/-   ##
==========================================
- Coverage   85.27%   85.26%   -0.02%     
==========================================
  Files         383      384       +1     
  Lines       22778    22795      +17     
  Branches      891      874      -17     
==========================================
+ Hits        19425    19436      +11     
+ Misses       3246     3245       -1     
- Partials      107      114       +7     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.