feat: scaffold deploy-scenario-network.yml

[just-mitch]

Add Scenario Network Deployment Workflow

This PR adds a new workflow for deploying a complete scenario network, which includes:

1. A new deploy-scenario-network.yml workflow that orchestrates the deployment of both an Ethereum devnet and rollup contracts

2. Updates to the deploy-eth-devnet.yml workflow to:

   • Accept a custom mnemonic as an input parameter
   • Expose deployment results (RPC URL, WebSocket URL, Beacon URL, Chain ID) as workflow outputs
   • Mask the mnemonic in logs for security

3. Updates to the Terraform configuration in deploy-eth-devnet:

   • Use the provided mnemonic instead of fetching from Google Secret Manager
   • Support both static IPs and cluster IPs for services
   • Add proper output handling for both IP types

4. Updates to the rollup contracts deployment to properly use the validators parameter

These changes enable more flexible and composable deployment workflows for testing scenarios.

[just-mitch]

• feat: spartan/bootstrap.sh network_deploy #16639 : 2 dependent PRs (#16648 , #16681 )
• feat: create test-network-scenarios.yml #16595
• feat: create deploy-aztec-infra.yml #16580
• feat: scaffold deploy-scenario-network.yml #16553 👈 (View in Graphite)
• feat: create deploy-rollup-contracts.yml #16549
• feat: deploy-eth-devnet.yml github action #16538
• next

This stack of pull requests is managed by Graphite. Learn more about stacking.

[alexghr]

should this be moved to the secret section of the workflow?

[just-mitch]

I'm not sure. If we only wanted it to be called via workflow_call, I'd say yes. But if we move it to secrets, then effectively whenever someone wants to manually dispatch, they'll be using the mnemonic stored in the repo, which I don't think is what we want.