Use github.action_ref for repo-sync checkout instead of hardcoded v1

github.action_ref resolves to whatever ref the caller used (e.g.
david/integration during testing, v1 in production), so the workflow
always checks out the matching version of the tooling.

Co-Authored-By: Oz <oz-agent@warp.dev>

Author: vorporeal

.github/workflows/escalation.yml

@@ -62,7 +62,7 @@ jobs:
       - uses: actions/checkout@v4
         with: { token: "${{ steps.token.outputs.token }}" }
       - uses: actions/checkout@v4
-        with: { repository: warpdotdev/repo-sync, ref: v1, path: .repo-sync, token: "${{ steps.token.outputs.token }}" }
+        with: { repository: warpdotdev/repo-sync, ref: ${{ github.action_ref }}, path: .repo-sync, token: "${{ steps.token.outputs.token }}" }
       - uses: actions/setup-python@v5
         with: { python-version: "3.12" }
       - run: pip install -e .repo-sync

.github/workflows/sync.yml

@@ -55,7 +55,7 @@ jobs:
       - uses: actions/checkout@v4
         with: { fetch-depth: 0, token: "${{ steps.token.outputs.token }}" }
       - uses: actions/checkout@v4
-        with: { repository: warpdotdev/repo-sync, ref: v1, path: .repo-sync, token: "${{ steps.token.outputs.token }}" }
+        with: { repository: warpdotdev/repo-sync, ref: ${{ github.action_ref }}, path: .repo-sync, token: "${{ steps.token.outputs.token }}" }
       - uses: actions/setup-python@v5
         with: { python-version: "3.12" }
       - run: pip install -e .repo-sync