feat(vm): add gateway changes to fast vm

[perekopskiy]

What ❔

Ports VM changes to vm_fast that are needed for gateway version. Code changes are mostly copied from vm_latest

Why ❔

vm_fast should support new protocol version

Checklist

• PR title corresponds to the body of PR (we generate changelog entries from PRs).
• Tests for the changes have been added / updated.
• Documentation comments have been added / updated.
• Code has been formatted via zkstack dev fmt and zkstack dev lint.

[slowli]

Would it be possible to unit-test pubdata logic in multivm? (I'd imagine by setting ProtocolVersionId to the gateway version.) AFAICT, pubdata-related fields are covered by shadow VM checks, so these tests could help checking that the relevant logic works identically for vm_latest and vm_fast. Can be done separately, of course.

[slowli]

Nit: clone() isn't necessary here.

Also, since pubdata_input is almost only read from the VM, so it could be relatively straightforward to return pubdata_input from this function (e.g., by supplying pubdata: Option<(&dyn PubdataBuilder, &mut PubdataInput)> to it), and then use it in finish_batch(). I'm not sure a similar transform would work for vm_latest though, and we'd probably want to keep BootloaderState equivalent for both (ideally, it'd make sense to share it).

[perekopskiy]

Removed clone.
Not sure I understood the point for returning pubdata_input, can you elaborate on why is it better than storing and reading it from BootloaderState?

[perekopskiy]

Would it be possible to unit-test pubdata logic in multivm?

Do you mean something particular? Rollup/Validium pubdata builders' logic is covered with tests in pubdata_builders module. We also have a vm test in sync-layer-stable that checks pubdata_inputs more thoroughly, it will be merged to main soonish.