feat: add scripts to validate phase2 output and parameter

[vmx]

This commit adds two scripts. One is to validate that the trusted
setup phase2 result matches the published parameter files.

The other one is to verify that a .params file (and the corresponding
.vk file) is part of the parameters.json.

[cryptonemo]

Looks good, but I'll approve after I have a chance to test

[DrPeterVanNostrand]

Maybe these scripts should live in the phase2-attestations repo? Which is where I putting the rest of the validation commands.

[cryptonemo]

Hrm, not sure, but I was thinking they could live here so that I can easily run them. Not that I can't get the other repo and test it out ...

Between both of you, what's the best way to verify and be happy with the merged files and the split v28 params that are output?

[DrPeterVanNostrand]

@nemo If this way is easier, then that's fine with me. I just wanted to ask

I was going to have participant's run split-keys on the merged phase2 files and then verify checksums against the v28 split files. I was probably going to re-upload the split files to s3

So something like this, which is in vmx's scripts:

$ ./phase2 split-keys <merged file>
$ split_digest=$(cat <.vk file> <.params file> <.contribs file> | b2sum | awk '{print $1}'); echo "${split_digest}  <merged file>" | b2sum -c

[porcuquine]

I approved pending @cryptonemo's test, if it can happen before we need this to test verification instructions.

[cryptonemo]

Verify phase2 script tested well.

[vmx]

I've split this PR into two pieces.

• The script to verify the parameters.json file makes sense to have in this repo, hence feat: add script to verify parameter checksums in parameters.json #1251
• The script to verify the trusted setup phase2 results now lives at the attestation repo: feat: add script to validate phase2 output phase2-attestations#3

The scripts are byte-identical to the ones of this PR.