fix: improve PAT_TOKEN handling and debugging in release workflow

- Add comprehensive debug output for token availability
- Fix environment variable access in git configuration step
- Use proper env vars instead of direct secret interpolation in shell
- Add explicit git remote verification steps

These changes should resolve the PAT_TOKEN not being recognized
properly, enabling bypass of branch protection rules in future releases.

Author: joshrotenberg

.github/workflows/cargo-workspaces-release.yml

@@ -74,17 +74,20 @@ jobs:
           PAT_TOKEN: ${{ secrets.PAT_TOKEN }}
 
       - name: Configure git
+        env:
+          PAT_TOKEN: ${{ secrets.PAT_TOKEN }}
+          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
         run: |
           git config user.name "github-actions[bot]"
           git config user.email "github-actions[bot]@users.noreply.github.com"
 
           # Configure git remote to use PAT_TOKEN for pushes
-          if [ -n "${{ secrets.PAT_TOKEN }}" ]; then
+          if [ -n "$PAT_TOKEN" ]; then
             echo "Configuring git to use PAT_TOKEN for pushes"
-            git remote set-url origin https://x-access-token:${{ secrets.PAT_TOKEN }}@github.com/${{ github.repository }}.git
+            git remote set-url origin https://x-access-token:[email protected]/${{ github.repository }}.git
           else
             echo "PAT_TOKEN not available, using GITHUB_TOKEN"
-            git remote set-url origin https://x-access-token:${{ secrets.GITHUB_TOKEN }}@github.com/${{ github.repository }}.git
+            git remote set-url origin https://x-access-token:[email protected]/${{ github.repository }}.git
           fi
 
           echo "Final git remote configuration:"