Epic: Multiple metrics in reexecution test

[RodrigoVillar]

At one point, we had multiple metrics in the reexecution tests (#4369) but we had to remove this as this resulted in our github-action-benchmark being corrupted (#4396). We should strive for our metrics to be as granular as possible and so this epic is catered towards that.

• Add back metervm (feat(reexecution/c): add back metervm #4509)
• Add Grafana visualizations for metervm metrics (feat: add metervm metrics for C-Chain avalanche-monitoring#36)
• Test custom metrics with GAB (chore: test custom metrics with github-action-benchmark. #4510)
  • We've decided that we want to use the custom benchmark feature of GAB
• Remove go bench in favor of custom benchmarks
  • Export CreateBlockChanFromLevelDB() (refactor(reexecute/c): export CreateBlockChanFromLevelDB #4638)
  • Switch TestExportBlockRange() from being a unit test to a separate binary (refactor: block export #4639)
  • Make BenchmarkReexecuteRange() into a binary (chore(reexecute/c): remove go bench from benchmark #4640)
• Add back multiple metrics in reexecution tests

[RodrigoVillar]

For adding Grafana visualizations, I noticed that in our HyperSDK dashboard, we have MeterVM metrics there (https://github.com/ava-labs/avalanche-monitoring/blob/main/grafana/dashboards/morpheusvm/performance.json). It may make sense to rip those metrics and place them into the C-Chain dashboard.