Fix concurrency groups in workflows

[epassaro]

Description

Trying to mimic the behavior of Azure Pipelines:

• Pushing two times to master should cancel the first run and build only for the latest commit
• Same for pushing to PRs
• Pushes to a certain PR shouldn't cancel other PRs builds
• Pushes to PRs shouldn't cancel master builds and vice-versa

See: https://docs.github.com/en/actions/using-workflows/workflow-syntax-for-github-actions#concurrency

Motivation and context

How has this been tested?

• Testing pipeline.
• Other.

Examples

Type of change

• Bug fix.
• New feature.
• Breaking change.
• None of the above.

Checklist

• My change requires a change to the documentation.
  • I have updated the documentation accordingly.
  • (optional) I have built the documentation on my fork following the instructions.
• I have assigned and requested two reviewers for this pull request.

[codecov]

Codecov Report

Merging #1998 (9e8136d) into master (37a9769) will not change coverage.
The diff coverage is n/a.

❗ Current head 9e8136d differs from pull request most recent head c41ce69. Consider uploading reports for the commit c41ce69 to get more accurate results

@@           Coverage Diff           @@
##           master    #1998   +/-   ##
=======================================
  Coverage   59.99%   59.99%           
=======================================
  Files          70       70           
  Lines        8111     8111           
=======================================
  Hits         4866     4866           
  Misses       3245     3245           

📣 Codecov can now indicate which changes are the most critical in Pull Requests. Learn more