ci(e2e): skip the run job on the changesets Release PR

The changesets/action "Version Packages" PR has head ref
`changeset-release/main` and is bot-generated — Railway never
spins up a preview for it. The e2e workflow's "Find Railway
preview deployment" step then fails fast with "No Railway
deployments exist for PR #N preview at all", and the resulting
red check on the Release PR is meaningless: there is no preview
to point e2e at, by design.

Skip the `run` job on PRs whose head ref is
`changeset-release/main`. This is the same skip-job-not-workflow
pattern already used by the `gate` job above: a skipped job
still reports conclusion=skipped to branch protection, which is
treated as passing, so the Release PR no longer carries a
spurious red check.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

Author: aspiers

.github/workflows/e2e-tests.yml

@@ -72,7 +72,18 @@ jobs:
     #
     # `always()` is needed because `gate` is skipped on non-PR
     # events, and GitHub would otherwise cascade-skip this job.
-    if: always() && (needs.gate.outputs.relevant == 'true' || github.event_name != 'pull_request')
+    #
+    # Skip the changesets/action "Version Packages" PR (head ref
+    # `changeset-release/main`): no Railway preview is provisioned
+    # for that bot-generated branch, so the "Find Railway preview
+    # deployment" step would always fail with "No Railway
+    # deployments exist for PR #N preview at all". A skipped *job*
+    # still reports conclusion=skipped to branch protection, which
+    # is treated as passing — same pattern as the `gate` job above.
+    if: >-
+      always() &&
+      github.event.pull_request.head.ref != 'changeset-release/main' &&
+      (needs.gate.outputs.relevant == 'true' || github.event_name != 'pull_request')
     runs-on: blacksmith-4vcpu-ubuntu-2404
     timeout-minutes: 20
     permissions: