feat: op-program supports custom chain config

[qizhou]

Description

This PR enables custom chain config in op-program-client to be part of the target binary (MIPS, RISCV64, etc) using go:embed. As a result, such custom config will be reflected in the absolute prestate hash, and thus be applied to the on-chain FDG.

Tests

After spinning up a devnet via make devnet-up, pass make verify-devnet under op-program folder.

Additional context

See https://discord.com/channels/1244729134312198194/1290708296939999242/1291598392853790752

Metadata

[ajsutton]

Sorry for the delay in reviewing this.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 64.04%. Comparing base (18732db) to head (ffd1f4a).
Report is 46 commits behind head on develop.

Additional details and impacted files

@@             Coverage Diff             @@
##           develop   #12310      +/-   ##
===========================================
- Coverage    64.23%   64.04%   -0.19%     
===========================================
  Files           52       52              
  Lines         4353     4353              
===========================================
- Hits          2796     2788       -8     
- Misses        1381     1390       +9     
+ Partials       176      175       -1     

Flag	Coverage Δ
cannon-go-tests	64.04% <ø> (-0.19%)	⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

see 1 file with indirect coverage changes

[ajsutton]

Looking good. Maybe the best way forward is to do the couple of nits around providing better error messages and leave this PR running op-program in process and merge it. Then do a follow up PR to make --network support a chain ID. That way we don't wind up creating too big a PR.

[qizhou]

Hi @ajsutton, let me know if you have further comments on this. Meanwhile, I am preparing the PR for supporting chain ID as network ID.

[ajsutton]

Sorry I lost track of what I'd said on this and was thinking we'd land the load-by-chain-id change first. But I'd said merge this and that probably does make more sense. I think it looks good so will get it merged in. The CI setup has changed a little in the mean time so I may have to jump a couple of hurdles but we'll get there. :)