Migrate release-snapshot workflow to JFrog proxy and large runner pool (#4898)

## Summary
- Use the new `setup-jfrog` composite action to proxy Go module
downloads through JFrog Artifactory
- Switch from `databricks-deco-testing-runner-group` to
`databricks-large-runner-group`
- Trigger workflow on changes to the `setup-jfrog` action

## Test plan
- [x] Verify the release-snapshot workflow succeeds on this PR

This pull request was AI-assisted by Isaac.

Author: pietern

.github/workflows/release-snapshot.yml

@@ -15,14 +15,19 @@ on:
       - reopened
     paths:
       - ".github/workflows/release-snapshot.yml"
+      - ".github/actions/setup-jfrog/**"
 
   workflow_dispatch:
 
 jobs:
   goreleaser:
     runs-on:
-      group: databricks-deco-testing-runner-group
-      labels: ubuntu-latest-deco
+      group: databricks-protected-runner-group-large
+      labels: linux-ubuntu-latest-large
+
+    permissions:
+      id-token: write
+      contents: write
 
     steps:
       - name: Checkout repository and submodules
@@ -31,6 +36,9 @@ jobs:
           fetch-depth: 0
           fetch-tags: true
 
+      - name: Setup JFrog
+        uses: ./.github/actions/setup-jfrog
+
       - name: Setup Go
         uses: actions/setup-go@4b73464bb391d4059bd26b0524d20df3927bd417 # v6.3.0
         with: