feat: create deploy-aztec-infra.yml

[just-mitch]

Add Deploy Aztec Infra Workflow and Refactor Deployment Workflows

One can:

lwfl deploy_scenario_network --input cluster=kind --input namespace=your-scenario​
# or
lwfl deploy_scenario_network --input cluster=aztec-gke-private --input namespace=your-scenario​

To get:

• an eth devnet
• gov and rollup contracts deployed
• aztec L2 infratructure deployed on top:
  • validators
  • rpc node
  • p2p bootstrap
  • prover stack

I renamed the deploy-staging-testnet​ to the more generic deploy-aztec-infra​, and made it correspondingly configurable.

Fix TMNT-178

AI Generated Summary

This PR adds a new GitHub workflow for deploying Aztec infrastructure and refactors existing deployment workflows to improve consistency and maintainability:

1. Added deploy-aztec-infra.yml workflow that:
   • Deploys a complete Aztec network infrastructure including P2P bootstrap nodes, validators, provers, and RPC nodes
   • Accepts configurable parameters for cluster, namespace, docker image, L1 connections, contract addresses, and resource profiles
2. Refactored existing deployment workflows:
   • Made required parameters explicitly required instead of using defaults
   • Added output variables to the rollup contracts deployment workflow to pass contract addresses to dependent workflows
   • Updated the scenario network deployment to use the new Aztec infra workflow
3. Improved Terraform configurations:
   • Reorganized the staging testnet Terraform to use a more modular approach with separate value files for different resource profiles
   • Simplified configuration by using dynamic blocks and local variables
   • Added support for local Terraform state for easier testing
   • Removed lifecycle blocks that prevented resource destruction
4. Enhanced deployment workflow integration:
   • Connected the ETH devnet, rollup contracts, and Aztec infra workflows in the scenario network deployment
   • Added support for prefunded mnemonic indices in the ETH devnet

These changes make the deployment process more flexible, maintainable, and consistent across different environments.

[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 👈 (View in Graphite)
• feat: scaffold deploy-scenario-network.yml #16553
• 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]

This is great. I'm a bit worried about removing the destruction protection on IP addresses since that would release those IPs to be used by something else but maybe we don't need to be so strict about them

[alexghr]

This is a very elegant approach!