Synthetic workload for benchmarking

Benchmarking Team would like to simulated the cost of a plutus transaction. This Issue is resolved once they have what they need.

Once Alonzo is integrated, the Benchmarking Team would be able to create scripts with the workload they want, so they wouldn't need the synthetic workload any longer. However, the synthetic workload might be easier to work with, even then, so they might want it despite not needing it.

And we may be able provide the synthetic workload before the Node Team has Alonzo integrated.

@deepfire offered that Consensus could specify where to introduce the synthetic load, and then Benchmarking could do the work.

In an ideal world, the result would be run-time configurable. But even if it's only configurable at compile-time, they could put that to use. (Maybe a shell environment variable would be a suitable compromise?)

Start by confirming with the Benchmarking and Consensus teams where the synthetic load should be introduced and which Plutus transaction cost it must simulate. Check the Alonzo integration status and clarify whether runtime, compile-time, or shell-environment configuration is required. Done means the Benchmarking Team can use the workload to simulate the requested transaction cost.

Written by the indexing model from the issue text.