Enhance support for switching production environment to "yellow"

[lightwalker-eth]

Background

• The current script for switching production environments doesn't explicitly support switching to "yellow": .github/workflows/deploy_switch_ensnode_environment.yml
• If we do switch the production environment to "yellow" it may cause the logic inside the "Promote ENSAdmin Vercel Deployment" step of the above script to break. See details in ./.github/scripts/promote_ensadmin.sh Specifically: the current logic in this promote_ensadmin.sh script assumes that each environment runs on Railway, but this isn't true for the "yellow" environment (or other potential future environments).

Goals

• Update the logic in the promote_ensadmin.sh script so that we create a more general mechanism for getting the related commit SHA dynamically from an ENSNode instance that doesn't rely specifically on any hosting provider's internal mechanics. Ex: Perhaps we introduce a strategy to include this data in the (public) ENSApi config?

[coderabbitai]

📝 CodeRabbit Plan Mode

Generate an implementation plan and prompts that you can use with your favorite coding agent.

• Create Plan

Examples

• Example 1
• Example 2

---

🔗 Related PRs

#1587 - feat(ci): include ENSNode v2 Sepolia instance in workflows config [merged]

---

🧪 Issue enrichment is currently in open beta.

You can configure auto-planning by selecting labels in the issue_enrichment configuration.

To disable automatic issue enrichment, add the following to your .coderabbit.yaml:

issue_enrichment:
  auto_enrich:
    enabled: false

💬 Have feedback or questions? Drop into our discord!