[test] Run proposal simulation for 1.16 on the new gas delta schedule

Slight change to rebase cleanly

Testing:

```
cargo run -p aptos-release-builder generate-proposals --release-config data/release.yaml --output-dir output

cargo run -p aptos-release-builder simulate-multi-step-proposal --network mainnet --proposal-dir output/sources/v1.16/step_1_upgrade_framework/
```

Simulation output seems to fail, is this expected? Did we catch a potential difference?
https://gist.github.com/perryjrandall/80d5b7f26594412cf5ae3e523084258b

aptos-move/aptos-release-builder/output/metadata/step_1_upgrade_framework.json

@@ -0,0 +1,6 @@
+{
+  "title": "Multi-step proposal to upgrade mainnet framework to v1.16",
+  "description": "This includes changes in https://github.com/aptos-labs/aptos-core/commits/aptos-release-v1.16",
+  "source_code_url": "https://github.com/aptos-labs/aptos-core",
+  "discussion_url": "https://github.com/aptos-labs/aptos-core"
+}

aptos-move/aptos-release-builder/src/simulate.rs

@@ -59,7 +59,7 @@ use move_core_types::{
     language_storage::{ModuleId, StructTag},
     move_resource::MoveResource,
 };
-use move_vm_types::resolver::ModuleResolver;
+use move_core_types::resolver::ModuleResolver;
 use once_cell::sync::Lazy;
 use parking_lot::Mutex;
 use std::{