#3973 Add functionality for testing transaction subsystem performance

[Anonymous]

Originally created by: dmkozh

Transaction simulation framework has been incompatible for some time and notably won't be compatible with Soroban. Thus we're removing it for now in order to reduce the maintenance burden.

Going forward, we'd probably want to introduce some similar framework that would account for protocol 20 changes in design, especially the Soroban support.

[Anonymous]

Originally posted by: marta-lokhova

To clarify here, the functionality we'll need here is specifically for testing performance of the transaction subsystem. Previously, this was achieved by taking a historical snapshot of a ledger, scaling it by some factor, then replaying scaled history on top, and profiling the results (note that this is different from performance testing of SCP/overlay that we do with supercluster). With Soroban, we'll need to rethink how we test perf, since we likely won't have much meaningful historical data for some time.