WASM PVM: Let the CI enforce that the hashes traces of V0 do not change

Context

Current owner: @picdc

We introduce a new script (run by the CI) which checks whether or not the hashes traces of the released versions of the WASM PVM do not change.

This is to ensure we don’t promote by mistake breaking changes 😅

Manually testing the MR

scripts/check_wasm_pvm_regressions.sh check

Then modify one of the v0 trace, and restart the script. See it fails.

Run

scripts/check_wasm_pvm_regressions.sh promote

Then run the check command again. See it passes.

Removes one of the v0 traces. See it fails.

Checklist

• Document the interface of any function added or modified (see the coding guidelines)
• Document any change to the user interface, including configuration parameters (see node configuration)
• Provide automatic testing (see the testing guide).
• For new features and bug fixes, add an item in the appropriate changelog (docs/protocols/alpha.rst for the protocol and the environment, CHANGES.rst at the root of the repository for everything else).
• Select suitable reviewers using the Reviewers field below.
• Select as Assignee the next person who should take action on that MR