chore: cleanup

[alexghr]

Fix A-2040

[greptile-apps]

Confidence Score: 4/5

The infrastructure cleanup appears safe to merge, with a non-blocking documentation mismatch for the retired RPC endpoints.

Findings

1.  Retired endpoints remain documented ▶

Summary

• Leaves only the canonical/v5 RPC deployments and image configuration.
• Updates the deploy-rpc README for the canonical-only configuration.
• Removes redundant fisherman settings after scaling the deployment to zero.
• The removed RPC hostnames remain advertised in an operational guide and should be retired there as well.

_{Reviews (1) · Last reviewed commit: "chore: cleanup"}

[greptile-apps]

Retired endpoints remain documented

Removing the v4 RPC entries also removes their backends, routes, certificates, and managed DNS hosts. However, the RPC operations guide still advertises v4.testnet.rpc.aztec-labs.com, testnet.rpc.aztec-labs.com, and v4.mainnet.rpc.aztec-labs.com as available endpoints. Operators following that guide will send requests to endpoints this Terraform configuration no longer provisions, so the references should be retired or redirected as part of this decommission. The same issue applies to the corresponding removal in spartan/terraform/deploy-rpc/environments/mainnet/main.tf:62.

[spalladino]

LGTM. Do we have metrics on whether anyone is hitting the v4 rpc?