WASM PVM: Freeze third version (used by Oxford)

What

Ensure that the regression traces related to the third revision of the PVM cannot be updated by mistake, by “freezing” the version.

Why

We don’t want to modify the behavior of the PVM for an already released revision by mistake. We will have to do the same with v4 when P is released (12th environment)

How

Update script-inputs/frozen_wasm_pvm_version, then run scripts/check_wasm_pvm_regressions.sh promote.

Manually testing the MR

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