chore: don't cancel concurrent main builds (#342)

Fixing this in all our rulesets.

This updates the GHA ci.yaml `concurrency` block to match all of our
other rule sets. In particular, the `cancel-in-progress` is updated to
_not_ cancel in progress main builds `${{ github.ref_name != 'main' }}`
so that if two commits land on main back-to-back the 2nd one does not
cancel the first if it is still running CI.

Author: gregmagolan

.github/workflows/ci.yaml

@@ -12,9 +12,10 @@ on:
   workflow_dispatch:
 
 concurrency:
-  # Cancel previous actions from the same PR: https://stackoverflow.com/a/72408109
-  group: ${{ github.workflow }}-${{ github.event.pull_request.number || github.ref }}
-  cancel-in-progress: true
+  # Cancel previous actions from the same PR or branch except 'main' branch.
+  # See https://docs.github.com/en/actions/using-jobs/using-concurrency and https://docs.github.com/en/actions/learn-github-actions/contexts for more info.
+  group: concurrency-group::${{ github.workflow }}::${{ github.event.pull_request.number > 0 && format('pr-{0}', github.event.pull_request.number) || github.ref_name }}${{ github.ref_name == 'main' && format('::{0}', github.run_id) || ''}}
+  cancel-in-progress: ${{ github.ref_name != 'main' }}
 
 jobs:
   test: