fix(lux-mainnet): EVM_CHAIN_IDS use canonical post-rebootstrap blockchain IDs

The hardcoded list had stale IDs from pre-rebootstrap chains:
  hanzo: cjhijar... → y5HBrn6E... (current)
  zoo:   2Y625Kvdd... → 2wbPWcyu... (current)
  pars:  2GiQb73Ce... → 2wYWjBHziTjf... (parsv4, 7B PARS)
  spc:   rtjwvtE1... and 2pUskxqaL5... → 2YTuJW9b1k... (spcv4, 11B SPC)

The stale IDs caused the per-pod upgrade.json to be written to chain-config
directories for blockchain IDs that no longer exist, while the actually-
running L2 EVMs at canonical IDs got no upgrade.json injection. EVM_CHAIN_IDS
now matches the same canonical IDs already in the chain-aliases stanza
below (and Agent D's lux-indexer ConfigMap commit 5f2a22ee).

NOTE: this changes which chain config dir gets the upgrade.json on next
pod restart. The 20-precompile + coronaThreshold list itself is
unchanged; reconciling it against the canonical 43-precompile +
coronaThreshold genesis is a separate (state-sensitive) operation that
needs planned downtime to avoid block-validity divergence.

k8s/lux-mainnet/luxd-startup.yaml

@@ -180,7 +180,10 @@ data:
     # This override activates Etna→Cancun, Fortuna, Granite from genesis.
     CHAIN_CONFIG_DIR="/data/configs/chains"
     UPGRADE_JSON='{"networkUpgradeOverrides":{"durangoTimestamp":0,"etnaTimestamp":0,"fortunaTimestamp":0,"graniteTimestamp":0},"precompileUpgrades":[{"aiMiningConfig":{"blockTimestamp":0}},{"blake3Config":{"blockTimestamp":0}},{"cggmp21Verify":{"blockTimestamp":0}},{"deadZeroConfig":{"blockTimestamp":0}},{"deadConfig":{"blockTimestamp":0}},{"deadFullConfig":{"blockTimestamp":0}},{"dexConfig":{"blockTimestamp":0}},{"routerConfig":{"blockTimestamp":0}},{"eciesConfig":{"blockTimestamp":0}},{"fheConfig":{"blockTimestamp":0}},{"frostVerify":{"blockTimestamp":0}},{"graphConfig":{"blockTimestamp":0}},{"hpkeConfig":{"blockTimestamp":0}},{"mldsaVerify":{"blockTimestamp":0}},{"mlkemConfig":{"blockTimestamp":0}},{"pqcryptoConfig":{"blockTimestamp":0}},{"ringConfig":{"blockTimestamp":0}},{"coronaThreshold":{"blockTimestamp":0}},{"slhdsaVerify":{"blockTimestamp":0}},{"zkConfig":{"blockTimestamp":0}}]}'
-    EVM_CHAIN_IDS="C cjhijarXPWx9ABpKJmhVvp5N3mfsNiX3u1Qpnas8cxTXwJAmK 2Y625Kvdd4wZ5LKx9kLSf1jGALyARmXVN1YsTb4F3Hzv4bPDbp 2GiQb73CeJESjc4omFv2YtQHZrRgJf25NXPzAr5J6UNHRcDV2F rtjwvtE1tEvrokmpeYdTq7b2zqZgmybKwR5MLjKMGAR1W78dQ 2pUskxqaL5Bpx7uRUGG1fDjPckjxQ4UKX4sLKeaS1NdSVBJd3F"
+    # Canonical L2 EVM blockchain IDs (in sync with /data/aliases.json below).
+    # Update both here and in the chain-aliases ConfigMap when a chain is
+    # re-bootstrapped (e.g. parsv4, spcv4, zoofix on testnet).
+    EVM_CHAIN_IDS="C y5HBrn6EWRMysSmH4nHA2sgpwgcjChJjQ7upSjWSwsrPeg4Cc 2wbPWcyuNUimWW7YMq3gymTTpHjP9Lsm7GpmcyWimEs9kyTAAH 2wYWjBHziTjfMJmUPZwsDdWhm96cWHo4vov1HPBmCYLXdbAZfM 2YTuJW9b1k7gDGgqZC58Wj6cT1qTzobx6SV8hiN22zT1L5qfHF"
     for CID in $EVM_CHAIN_IDS; do
       mkdir -p "${CHAIN_CONFIG_DIR}/${CID}"
       echo "$UPGRADE_JSON" > "${CHAIN_CONFIG_DIR}/${CID}/upgrade.json"