ref(actions): allow more flexibility on cached states usage

[gustavovalverde]

Motivation

We've added the possibility to deploy instances with a cached state attached, but we might also want to deploy them without it, or change the cached state disk preference depending on the github source, while not affecting our actual deployment process.

Solution

• Allow to select a cached state based on:
  • Type of cached disk to use (tip or checkpoint)
  • Source (main branch vs PR or any other available)
  • Network
• Allow to deploy a node without cached state
• Search for branch/PR reference instead of commit (as this is an use case that we haven't used for a while)
• Improve the disk selection logic, by allowing a preference for cached states from the main branch, without disallowing finding other available disks

Tests

• Deployed to Testnet with a cached state: https://github.com/ZcashFoundation/zebra/actions/runs/11162158270
• Deployed to Testnet without a cached state: https://github.com/ZcashFoundation/zebra/actions/runs/11163638750 (get disk is skipped and instance is deployed without a cached state attached).

Follow-up Work

Support the matrix use case when releasing a new Zebra version:

zebra/.github/workflows/cd-deploy-nodes-gcp.yml

Line 233 in 2552c3c

name: Deploy ${{ matrix.network }} nodes

PR Author's Checklist

• The PR name will make sense to users.
• The PR provides a CHANGELOG summary.
• The solution is tested.
• The documentation is up to date.
• The PR has a priority label.

PR Reviewer's Checklist

• The PR Author's checklist is complete.
• The PR resolves the issue.

[upbqdn]

@gustavovalverde can you update this branch? I can't do it.

[gustavovalverde]

@upbqdn this one should be ready to merge