ci(release): switch to grdsdev/melos-action fork with token support

Use grdsdev/melos-action@feat/custom-token-for-create-pr across all three
release workflows. Pass the App token to the melos-action in release-prepare
so peter-evans/create-pull-request uses it directly — the fork's token input
is the correct fix for the GITHUB_TOKEN PR creation restriction.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

Author: grdsdev

.github/workflows/release-prepare.yml

@@ -42,9 +42,10 @@ jobs:
           cache: true
 
       - name: Setup Melos
-        uses: bluefireteam/melos-action@v3
+        uses: grdsdev/melos-action@feat/custom-token-for-create-pr
         with:
           run-versioning: ${{ inputs.prerelease == false }}
           run-versioning-prerelease: ${{ inputs.prerelease == true }}
           run-versioning-graduate: ${{ inputs.graduate == true }}
           create-pr: true
+          token: ${{ steps.app-token.outputs.token }}

.github/workflows/release-publish.yml

@@ -44,7 +44,7 @@ jobs:
           cache: true
 
       - name: Bootstrap with Melos
-        uses: bluefireteam/melos-action@v3
+        uses: grdsdev/melos-action@feat/custom-token-for-create-pr
 
       - name: Publish dry run
         run: melos publish --scope ${{ inputs.package-name }} --dry-run

.github/workflows/release-tag.yml

@@ -36,7 +36,7 @@ jobs:
           cache: true
 
       - name: Setup Melos
-        uses: bluefireteam/melos-action@v3
+        uses: grdsdev/melos-action@feat/custom-token-for-create-pr
         with:
           tag: true
       - name: Trigger publish workflows