Respect block limits when fetching transactions from persistence #330
Description
Currently we retrieve all transactions that are stored in the TransactionStorage, then order/simulate them, and only then apply the given limit.
This is very bad for performance for cases where the mempool is filled and will create a lot of performance and memory bottlenecks in those cases.
A fix for this would be (since we don't know what percentage of transactions will be skipped/removed) to retrieve transactions just in time by the execution module