op-program: Verify prestate reproducibility against releases.json

[ajsutton]

Description

Modifies the op-program prestates reproducibility job to automatically build all op-program tags and compare the results against releases.json which is used by superchain-registry. This will ensure the two files stay in sync.

Also reviewed the op-program releases that have been submitted to governance and removed the governanceApproved flag from some which were never deployed to op-mainnet and not submitted in governance proposals.

The build-prestates.sh script now creates a JSON file that lists the version and hash of each built prestate.

[ajsutton]

As part of this I did some historical digging so if anyone winds up here wondering why certain releases were marked as not governance approved...

The three governance approved releases currently are:
1.0.0 - initial fault proofs release
1.2.0 - Fjord
1.3.1 - Granite
which are the only thee prestates used in any games on op-mainnet

op-sepolia has used four prestates:
0.2.0 (probably fault proof alpha chad)
0.3.1/1.0.0 (same commit - likely was 0.3.1 when deployed to sepolia and then tagged as the 1.0.0 release for op-mainnet)
1.1.0 (problaby Fjord and likely should have been an rc with the final release only tagged for mainnet)
1.3.0-rc.3 (Granite)

the devnet has also used four:
0.3.0 (I think this was the initial fault proof release and we then found a bug and did a second upgrade - we didn't release alpha chad to devnet as it wasn't integrated with the OptimismPortal could be deployed straight to op-sepolia without any risk)
0.3.1/1.0.0 (initial fault proof release)
1.1.0 (probably Fjord and should have been an RC)
1.3.0-rc.2