ci: pin solana-cli-version to 3.1.10 in all workflows

heyAyushh/setup-solana@v5.9 (used directly in native/pinocchio/quasar
and transitively via heyAyushh/setup-anchor@v4.999 in anchor.yml) has
an intermittently broken 'stable' resolver. When the upstream
STABLE_CHANNEL_LATEST_TAG env var is unset/empty in a given run, the
action logs 'Using Solana CLI version ' (no version) and then curls
https://release.anza.xyz/v/install, which returns HTTP 404 and fails
the job. Recent main-branch CI run 25696483414 (Anchor) is a concrete
example.

The action is already at its latest tag (v4.999 / v5.9 follow a
non-standard '4.99X / 5.X' floating-tag scheme where higher = newer)
and the maintainer's most recent commit message is literally 'bumped
action because of solana stable' — i.e. upstream is aware of the
brittleness but consumers still get 'stable' as the de facto default.
Pinning a concrete version is the only defensive answer available to
us.

3.1.10 is the Solana CLI version recommended by Anchor 1.0.0's release
notes and pinned by Anchor's own CI from 1.0.0-rc.5 onward (see the
Anchor CHANGELOG). It is also compatible with our anchor-version:
1.0.0 pin. The non-anchor frameworks are pinned to the same value to
keep the CI matrix consistent.

The 'beta' steps in native.yml and pinocchio.yml are intentionally
left floating: they are the channel-tracking jobs and are already
marked continue-on-error with a comment explaining the upstream beta
404 behaviour.

A separate issue will be filed upstream at heyAyushh/setup-solana
documenting the empty-version resolver bug.

Bump in lockstep with anchor-version when upgrading Anchor.

Author: Edward (Mike's sidekick)

.github/workflows/anchor.yml

@@ -138,7 +138,14 @@ jobs:
       - uses: heyAyushh/setup-anchor@v4.999
         with:
           anchor-version: 1.0.0
-          solana-cli-version: stable
+          # Pinned to 3.1.10 (not `stable`) because heyAyushh/setup-anchor's
+          # `stable` resolver intermittently returns an empty version string,
+          # which makes the action curl https://release.anza.xyz/v/install and
+          # 404. 3.1.10 is the version recommended by Anchor 1.0.0's release
+          # notes and pinned by Anchor's own CI in 1.0.0-rc.5+. Bump in lockstep
+          # with anchor-version above. See upstream issue tracking the brittle
+          # `stable` behaviour.
+          solana-cli-version: 3.1.10
       - name: Install Surfpool
         run: curl -sL https://run.surfpool.run/ | bash
       - name: Display Versions

.github/workflows/native.yml

@@ -222,7 +222,16 @@ jobs:
       - name: Setup Solana Stable
         uses: heyAyushh/setup-solana@v5.9
         with:
-          solana-cli-version: stable
+          # Pinned to 3.1.10 (not `stable`) because heyAyushh/setup-solana's
+          # `stable` resolver intermittently returns an empty version string,
+          # which makes the action curl https://release.anza.xyz/v/install and
+          # 404. 3.1.10 is the version recommended by Anchor 1.0.0's release
+          # notes; we use it here too to keep the matrix consistent across
+          # frameworks. The `beta` step below intentionally stays floating —
+          # it's the channel-tracking job and is already marked
+          # continue-on-error. See upstream issue tracking the brittle `stable`
+          # behaviour.
+          solana-cli-version: 3.1.10
       - name: Build and Test with Stable
         run: |
           source build_and_test.sh

.github/workflows/pinocchio.yml

@@ -222,7 +222,16 @@ jobs:
       - name: Setup Solana Stable
         uses: heyAyushh/setup-solana@v5.9
         with:
-          solana-cli-version: stable
+          # Pinned to 3.1.10 (not `stable`) because heyAyushh/setup-solana's
+          # `stable` resolver intermittently returns an empty version string,
+          # which makes the action curl https://release.anza.xyz/v/install and
+          # 404. 3.1.10 is the version recommended by Anchor 1.0.0's release
+          # notes; we use it here too to keep the matrix consistent across
+          # frameworks. The `beta` step below intentionally stays floating —
+          # it's the channel-tracking job and is already marked
+          # continue-on-error. See upstream issue tracking the brittle `stable`
+          # behaviour.
+          solana-cli-version: 3.1.10
       - name: Build and Test with Stable
         run: |
           source build_and_test.sh

.github/workflows/quasar.yml

@@ -197,7 +197,13 @@ jobs:
       - name: Setup Solana Stable
         uses: heyAyushh/setup-solana@v5.9
         with:
-          solana-cli-version: stable
+          # Pinned to 3.1.10 (not `stable`) because heyAyushh/setup-solana's
+          # `stable` resolver intermittently returns an empty version string,
+          # which makes the action curl https://release.anza.xyz/v/install and
+          # 404. 3.1.10 is the version recommended by Anchor 1.0.0's release
+          # notes; using it here keeps the matrix consistent across frameworks.
+          # See upstream issue tracking the brittle `stable` behaviour.
+          solana-cli-version: 3.1.10
       - name: Install Quasar CLI
         # Pinned to quasar rev 3d6fb0d8 (the HEAD this migration was written
         # against, immediately after PRs #195 + #196). The next merged PR