Verify updates to GasSchedule against native schedule

[supra-yoga]

Description

PR #292 aims to deliver the tooling required to update an on-chain GasSchedule. This tooling was put to use during QA testing of SMR-Moonshot v10.0.4 and an issue was detected as described here. The following changes must be made to the #292 to ensure stability when upgrading GasSchedule:

The tool must ensure that:

1. All gas parameters present in the native schedule for the environment are at the same (or lower) version as a newly generated on-chain schedule are included in the generated schedule.
2. Compare the entries of the generated schedule to the keys of the native schedule of the binary used to generate the schedule, where said keys belong to a version equal to or less than the version of the generated schedule
3. The tool must also refuse to generate the schedule if the requested gas feature version is greater than the native gas feature version to reduce the likelihood of it being unable to detect missing entries.

[supra-yoga]

Feasibility check for the above requirements:

1. All gas parameters present in the native schedule for the environment are at the same (or lower) version as a newly generated on-chain schedule are included in the generated schedule.

This cannot be accomplished as the on-chain resource 0x1::gas_schedule::GasScheduleV2 does not return the versions of the parameters individually.

2. Compare the entries of the generated schedule to the keys of the native schedule of the binary used to generate the schedule, where said keys belong to a version equal to or less than the version of the generated schedule

Comparing the keys can be accomplished, whereas comparing the versions of the individual parameter will not be possible because of the same reason as the above point.

3. The tool must also refuse to generate the schedule if the requested gas feature version is greater than the native gas feature version to reduce the likelihood of it being unable to detect missing entries.

Feasible by simply comparing the gas feature versions of the native and the generated schedule.

[supra-yoga]

Additionally, the tooling currently allows removal of gas parameters. This cannot be permitted because removing a parameter from the generated schedule would also mean the same parameter must be removed from the Native schedule in the environment in which it is to be deployed. Therefore, the tooling should not facilitate the removal of gas parameters.