[benchmark] Add option for package overrides

[georgemitenkov]

Description

This PR adds support for package overriding: one can specify --override-packages P1 P2 P3 and replay historical transactions with new code (e.g., framework). This allows to check performance (benchmark option) or gas usage (diff option).

Note: one needs to be careful overriding packages which add new package dependencies. For example, it is possible that stdlib adds a module, which is used in framework code. For override, one needs to provide both packages.

How Has This Been Tested?

Key Areas to Review

Type of Change

• New feature

Which Components or Systems Does This Change Impact?

• Other (specify)

Checklist

• I have read and followed the CONTRIBUTING doc
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I identified and added all stakeholders and component owners affected by this change as reviewers
• I tested both happy and unhappy path of the functionality
• I have made corresponding changes to the documentation

[trunk-io]

⏱️ 27m total CI duration on this PR

Job	Cumulative Duration	Recent Runs
check-dynamic-deps	14m	🟩 🟩 🟩 🟩 🟩
rust-cargo-deny	8m	🟩 ⬜ 🟩 🟩 🟩
general-lints	2m	🟩 ⬜ 🟩 🟩 🟩
semgrep/ci	2m	🟩 🟩 🟩 🟩 🟩
file_change_determinator	1m	🟩 🟩 🟩 🟩 🟩
permission-check	17s	🟩 🟩 🟩 🟩 🟩
permission-check	15s	🟩 🟩 🟩 🟩

_{settings ⋅ feedback ⋅ docs ⋅ learn more about trunk.io}

[georgemitenkov]

• [benchmark] Add option for package overrides #15841 👈 (View in Graphite)
• main

This stack of pull requests is managed by Graphite. Learn more about stacking.

[vineethk]

Looks great and a very useful functionality. Left a few minor comments.

[vineethk]

Another cool feature this brings (and I think we should be explicit about it in the readme) is that you can compile using different compiler versions/optimization levels/experimental compiler stuff and just point to the built packages, giving the ability to compare them.

[georgemitenkov]

Yes yes yes! Exactly, but for that I need to modify CLI to pass flags to build option, or instead get already build packages from the path (ideally)

[vineethk]

Ah, so this would allow pointing to just source. Perhaps mention that right now, the build option is only used for getting the bytecode version (and that this wont recompile the package with move-2).

[georgemitenkov]

Right now compilation happens with hardcoded options, ideally one should be able to paramterize this, do you have specific things in mind I should add? e.g., how do I enable optimization levels, etc.

My original plan was to point to already build package (so that using compiler is external), but I did not find a way to retrieve the package from the filesystem (i.e., we don't have APIs for that, etc.) so instead just used this for now. You can probably suggest more here from compiler side?