Hard code workflow name and cancel-in-progress only for PRs (#23431)

This changes the names of concurrency groups in most of our workflows to
use their hard-coded names instead of the name of the workflow that
triggered them (e.g. `build-wasm-...` and `build-binaries-...` instead
of `Release -...` for both). Hopefully this will reduce the number of
times the jobs butt heads.

I did not make this change for the CI workflow or for the Daily Fuzz
workflow since it didn't seem relevant for those, but let me know if I
should.

Author: dylwil3

.github/workflows/build-binaries.yml

@@ -20,8 +20,8 @@ on:
       - .github/workflows/build-binaries.yml
 
 concurrency:
-  group: ${{ github.workflow }}-${{ github.ref }}
-  cancel-in-progress: true
+  group: build-binaries-${{ github.ref }}
+  cancel-in-progress: ${{ github.event_name == 'pull_request' }}
 
 permissions: {}
 

.github/workflows/build-wasm.yml

@@ -15,8 +15,8 @@ on:
       - .github/workflows/build-wasm.yml
 
 concurrency:
-  group: ${{ github.workflow }}-${{ github.ref }}
-  cancel-in-progress: true
+  group: build-wasm-${{ github.ref }}
+  cancel-in-progress: ${{ github.event_name == 'pull_request' }}
 
 permissions: {}
 

.github/workflows/memory_report.yaml

@@ -25,8 +25,8 @@ on:
       - "!crates/ty_python_semantic/resources/corpus/**"
 
 concurrency:
-  group: ${{ github.workflow }}-${{ github.ref_name }}-${{ github.event.pull_request.number || github.sha }}
-  cancel-in-progress: true
+  group: memory-report-${{ github.ref_name }}-${{ github.event.pull_request.number || github.sha }}
+  cancel-in-progress: ${{ github.event_name == 'pull_request' }}
 
 env:
   CARGO_INCREMENTAL: 0

.github/workflows/mypy_primer.yaml

@@ -25,8 +25,8 @@ on:
       - "!crates/ty_python_semantic/resources/corpus/**"
 
 concurrency:
-  group: ${{ github.workflow }}-${{ github.ref_name }}-${{ github.event.pull_request.number || github.sha }}
-  cancel-in-progress: true
+  group: mypy-primer-${{ github.ref_name }}-${{ github.event.pull_request.number || github.sha }}
+  cancel-in-progress: ${{ github.event_name == 'pull_request' }}
 
 defaults:
   run:

.github/workflows/publish-ty-playground.yml

@@ -15,8 +15,8 @@ on:
       - ".github/workflows/publish-ty-playground.yml"
 
 concurrency:
-  group: ${{ github.workflow }}-${{ github.ref_name }}
-  cancel-in-progress: true
+  group: publish-ty-playground-${{ github.ref_name }}
+  cancel-in-progress: ${{ github.event_name == 'pull_request' }}
 
 env:
   CARGO_INCREMENTAL: 0

.github/workflows/ty-ecosystem-analyzer.yaml

@@ -13,8 +13,8 @@ on:
       - reopened
 
 concurrency:
-  group: ${{ github.workflow }}-${{ github.ref_name }}-${{ github.event.pull_request.number || github.sha }}
-  cancel-in-progress: true
+  group: ty-ecosystem-analyzer-${{ github.ref_name }}-${{ github.event.pull_request.number || github.sha }}
+  cancel-in-progress: ${{ github.event_name == 'pull_request' }}
 
 env:
   CARGO_INCREMENTAL: 0

.github/workflows/typing_conformance.yaml

@@ -25,8 +25,8 @@ on:
       - "!crates/ty_python_semantic/resources/corpus/**"
 
 concurrency:
-  group: ${{ github.workflow }}-${{ github.ref_name }}-${{ github.event.pull_request.number || github.sha }}
-  cancel-in-progress: true
+  group: typing-conformance-${{ github.ref_name }}-${{ github.event.pull_request.number || github.sha }}
+  cancel-in-progress: ${{ github.event_name == 'pull_request' }}
 
 env:
   CARGO_INCREMENTAL: 0