chore: upgrade testnet/devnet Aztec to 5.0.0-rc.2

[FilipHarald]

Summary

• Upgrade Aztec JS/package dependencies and lockfile to 5.0.0-rc.2.
• Update testnet/devnet compiler images and local sandbox/compiler config to 5.0.0-rc.2.
• Keep mainnet compiler pinned to 4.2.0 because Aztec v5 is not intended for mainnet yet.
• Recompile event-cannon Aztec contracts and regenerate codegen artifacts for 5.0.0-rc.2.
• Adapt to Aztec SDK API changes (AztecAddress.fromStringUnsafe) and fix BigInt JSON serialization for validator totals.

Verification

• yarn install
• yarn build
• yarn workspace @chicmoz/explorer-api test-once tests/unit/l2-tips-native-status.test.ts
• aztec compile && aztec codegen target --outdir ../../artifacts for:
  • SimpleLogging
  • SimpleLoggingUpdate
  • ExplorerShowcase
• Local minikube testnet smoke test via skaffold run -f k8s/local/skaffold.testnet.yaml
  • /health OK
  • /l2/latest-height OK
  • /l2/tips OK with degraded: false
  • /l1/l2-validators/totals OK
  • manual L2 tips canary job completed

Live deploy checklist

• Confirm testnet/devnet images use 5.0.0-rc.2; confirm mainnet compiler remains 4.2.0.
• Watch rollouts for aztec-listener, ethereum-listener, explorer-api, websocket-event-publisher, and compiler-orchestrator.
• Check Aztec listener logs for successful RPC calls, chain info events, block catchup, and no repeated RPC failures.
• Check Ethereum listener logs for expected L1 chain (ETH_SEPOLIA on testnet, ETH_MAINNET on mainnet) and L1 event indexing.
• Smoke API endpoints: /health, /l2/latest-height, /l2/blocks/latest, /l2/tips, /l2/rpc-nodes, /l1/l2-validators/totals.
• Confirm /l2/tips is not stale/degraded after catchup settles.
• Check Kafka consumers join the right network-prefixed groups/topics.
• Verify gateway/auth path rewrite works: /v1/<api-key>/l2/latest-height.
• Verify compiler/contract verification path with one artifact if compiler-orchestrator is deployed.
• Check websocket event flow for new blocks/finalization updates.

Notes

• During local minikube testing, CoreDNS needed external DNS forwarding fixed for Aztlan RPC hostnames; this was local-cluster-only and is not part of the PR.