fix: add moved block for p2p_bootstrap helm release

[AztecBot]

What

Adds a Terraform moved block so the p2p bootstrap helm release refactor from #24220 does not destroy and recreate the running bootstrap node.

moved {
  from = helm_release.releases["p2p_bootstrap"]
  to   = helm_release.p2p_bootstrap[0]
}

Why

#24220 ("deploy internal p2p bootnodes first") pulled p2p_bootstrap out of the helm_releases map — where it was instantiated via helm_release.releases["p2p_bootstrap"] — into its own helm_release.p2p_bootstrap resource (with count, addressed as helm_release.p2p_bootstrap[0]) so it could be applied before the rest of the releases.

To Terraform those are two distinct resource addresses, so without a moved block a terraform apply against an existing network plans to destroy helm_release.releases["p2p_bootstrap"] and create helm_release.p2p_bootstrap[0], tearing down and recreating the live bootstrap node. The moved block tells Terraform they are the same release, so it updates in place instead.

The block is safe for networks deployed without an internal bootnode: when DEPLOY_INTERNAL_BOOTNODE is false the source address never existed in state and the moved is a no-op.

Testing

• terraform fmt -check passes.
• terraform init -backend=false + terraform validate → Success! The configuration is valid.

Refs #24220

---

Created by claudebox · group: slackbot