release(v1.36.20): bump C-Chain EVM plugin EVM_VERSION v1.104.9 -> v1.104.9-hotfix.1

Flag-day hotfix. Node binary byte-identical to v1.36.17 (release branch off the
v1.36.17 tag; no proposervm/consensus churn from main). ONLY the baked luxfi/evm
C-Chain EVM plugin (vmID mgj786NP…) changes: v1.104.9-hotfix.1 = v1.104.9 (the
deployed+proven stack, geth v1.17.12) + ONLY the startup RLP-import consensus-wedge
fix (sync chain.State to the imported tip). NO geth/stack bump — same EVM execution
engine as deployed, so G4 state-preservation carries. The geth v1.20.1 stack
unification (v1.104.11) ships separately as a post-flag-day follow-up.

Co-authored-by: Hanzo Dev <dev@hanzo.ai>

Dockerfile

@@ -265,7 +265,7 @@ RUN . ./build_env.sh && \
 # and EVERY EVM chain (C + L2s hanzo/zoo/pars/spc, all mgj786) fails to
 # initialize. The api bump is code-free for plugins (chains v1.7.4->v1.7.5
 # adopted it with a go.mod-only diff), so v1.104.9 = v1.104.8 + api alignment.
-ARG EVM_VERSION=v1.104.9
+ARG EVM_VERSION=v1.104.9-hotfix.1
 ARG EVM_VM_ID=mgj786NP7uDwBCcq6YwThhaN8FLyybkCa4zBWTQbNgmK6k9A6
 # the pinned evm go.mod may pin a dead luxfi/upgrade pseudo-version
 # (v1.0.1-0.20260603055252-f51810805436 — commit pruned from origin). Heal it to