[CI]: Add Concurrency Grouping to GitHub Workflows

[Ishani217]

What problem is this PR solving?

fixes #1437

Description of the changes

• Whenever we push commits to a PR, workflows are triggered for that commit. After that, if we push additional commits to this PR, workflows in Github Actions run on both commits.
• We need to cancel the previous run and run only on the most recent pushed commit. This would help save some GitHub Action Minutes (probably not a problem for this project but its always better to same some resources) and unexpected workflow failures on previous commits.

[ArthurSens]

Thanks for the PR! If I understand it correctly, if we accept the PR as it is, we would be canceling workflows if we merge 2 or more PRs to main in a short period, is that correct?

Ideally, we never want to cancel workflows on pushes to the main branch to make sure it is easy to find commits that break our workflows

[Ishani217]

@ArthurSens Nice catch actually :)
If two PRs would be merged in a timeframe when their workflow runs are concurrent, then yes, previous PR's commit push workflow trigger would be cancelled.

I need to close this PR then, since we aren't using merge queues to handle that case

[bwplotka]

So surprised this is not by default for PRs. Thanks!

I only hope we DO NOT cancel on main. Let's try this out, we can always revert.