PLT-9014 Query volume benchmarking for Marlowe Runtime

[bwbush]

This PR provides configurable volume/load tests for the following Marlowe Runtime protocols:

• BulkSync
• HeaderSync
• Sync
• Query

See https://github.com/input-output-hk/marlowe-cardano/tree/PLT-9014/marlowe-benchmark#readme for documentation and example output.

Subsequent PRs will address other protocols and data management for reporting.

Pre-submit checklist:

• Branch
  • Tests are provided (if possible)
  • Test report is updated (if relevant)
  • Commit sequence broadly makes sense
  • Key commits have useful messages
  • Relevant tickets are mentioned in commit messages
  • Formatting, PNG optimization, etc. are updated
  • Operables are updated with changes to executable command line options.
  • Deploy charts updated with changes to operables.
• PR
  • Self-reviewed the diff
  • Useful pull request description
    • Review required
    • Substantial changes to code, test, or documentation
    • Change made to Marlowe validator (@bwbush and @palas must be included as reviewers)
    • Review not required
    • Minor changes to non-critical code, documentation, nix derivations, configuration files, or scripts
    • Formatting, spelling, grammar, or reorganization
  • Reviewer requested

[jhbertra]

Note because MarloweQueryClient is a monad this could be

Suggested change

	Statistics{..} <- foldlM ((runMarloweQueryClient .) . benchmark start pageSize) def filters
	Statistics{..} <- runMarloweQueryClient $ foldlM (benchmark start pageSize) def filters

The difference is that you don't establish a new connection for each filter. I'll leave it up to you to decide if this is what you want or not.

[bwbush]

I kept that foldM outermost because I thought that might be a bit more stressful to the backend service. Normally, I would have put runMarloweQueryClient on the outside, for efficiency.

[jhbertra]

Nice, I think this a good place to start the design.