Run integration test workflow on release branch creation

The project uses the standard GitHub Actions convention of providing a major version ref. A branch  is used for that
purpose.

These release branches may contain a subset of the history of the default branch. Although most often this would mirror
the history on the `main` branch, in some cases it might be beneficial to cherry-pick the commits ready for release to
the release branch, excluding other commits that are not yet ready for release.

The status of the GitHub Actions workflows should be evaluated before making a release. However, this is not so simple
as checking the status of the commit at the tip of the release branch. The reason is that, for the sake of efficiency,
the workflows are configured to run only when the processes are relevant to the trigger event (e.g., no need to run unit
tests for a change to the readme).

In the case of the default branch, you can simply set the workflow runs filter to that branch and then check the result
of the latest run of each workflow of interest. However, that was not possible to do with the release branch since it
might be that the workflow was never run in that branch. The status of the latest run of the workflow in the default
branch might not match the status for the release branch if the release branch does not contain the full history.

For this reason, it will be helpful to trigger all relevant workflows on the creation of a release branch. This will
ensure that each of those workflows will always have at least one run in the release branch. Subsequent commits pushed to
the branch can run based on their usual trigger filters and the status of the latest run of each workflow in the branch
will provide an accurate indication of the state of that branch.

Branches are created for purposes other than releases, most notably feature branches to stage work for a pull request.
Because the collection of workflows in a Tooling project are often very comprehensive, it would not be convenient or
efficient to run them on the creation of every feature branch.

Unfortunately, GitHub Actions does not support filters on the `create` event of branch creation like it does for the
`push` and `pull_request` events. There is support for a `branches` filter of the `push` event, but that filter is an AND
to the `paths` filter and this application requires an OR. For this reason, the workflows must be triggered by the
creation of any branch. The unwanted job runs are prevented by adding a `run-determination` job with the branch filter
handled by Bash commands. The other jobs of the workflow use this `run-determination` job as a dependency, only running
when it indicates they should via a job output. Because this minimal `run-determination` job runs very quickly, it is
roughly equivalent to the workflow having been skipped entirely for non-release branch creations.

Author: per1234

.github/workflows/test-integration.yml

@@ -1,6 +1,8 @@
 name: Run integration tests
 
 on:
+  create:
+
   pull_request:
     paths:
       - ".github/workflows/test-integration.yml"
@@ -28,7 +30,32 @@ env:
   TESTDATA_REPORTS_PATH: .github/workflows/testdata/reports
 
 jobs:
+  run-determination:
+    runs-on: ubuntu-latest
+    outputs:
+      result: ${{ steps.determination.outputs.result }}
+    steps:
+      - name: Determine if the rest of the workflow should run
+        id: determination
+        run: |
+          RELEASE_BRANCH_REGEX="^refs/heads/v[0-9]+$"
+          # The `create` event trigger doesn't support `branches` filters, so it's necessary to use Bash instead.
+          if [[
+            "${{ github.event_name }}" != "create" ||
+            "${{ github.ref }}" =~ $RELEASE_BRANCH_REGEX
+          ]]; then
+            # Run the other jobs.
+            RESULT="true"
+          else
+            # There is no need to run the other jobs.
+            RESULT="false"
+          fi
+
+          echo "result=$RESULT" >> $GITHUB_OUTPUT
+
   default-inputs:
+    needs: run-determination
+    if: needs.run-determination.outputs.result == 'true'
     runs-on: ubuntu-latest
 
     steps:
@@ -49,6 +76,8 @@ jobs:
         uses: ./extras/compile-sketches
 
   all-inputs:
+    needs: run-determination
+    if: needs.run-determination.outputs.result == 'true'
     runs-on: ubuntu-latest
 
     strategy:
@@ -120,6 +149,8 @@ jobs:
 
   multiple-steps:
     name: multiple-steps (${{ matrix.board.source-type }})
+    needs: run-determination
+    if: needs.run-determination.outputs.result == 'true'
     runs-on: ubuntu-latest
 
     strategy:
@@ -209,6 +240,8 @@ jobs:
             - examples/Sweep
 
   python-package-dependency:
+    needs: run-determination
+    if: needs.run-determination.outputs.result == 'true'
     runs-on: ubuntu-latest
 
     steps:
@@ -239,6 +272,8 @@ jobs:
 
   # Targeted testing for ESP32 boards platform support.
   pyserial-dependency:
+    needs: run-determination
+    if: needs.run-determination.outputs.result == 'true'
     runs-on: ubuntu-latest
 
     steps:
@@ -267,7 +302,10 @@ jobs:
             - ${{ env.TESTDATA_SKETCHES_PATH }}/BareMinimum
 
   check-sketches-reports:
-    needs: all-inputs
+    needs:
+      - run-determination
+      - all-inputs
+    if: needs.run-determination.outputs.result == 'true'
     runs-on: ubuntu-latest
 
     steps:
@@ -334,6 +372,8 @@ jobs:
           exit $EXIT_STATUS
 
   expected-failed-compilation:
+    needs: run-determination
+    if: needs.run-determination.outputs.result == 'true'
     runs-on: ubuntu-latest
 
     steps: