Ledger browser performance with high number of transactions

As the number of transactions on the ledger grows, the ledger browser struggles more and more to execute queries filtering the data based on the requested parameters.

In particular, we are noticing on BCovrin Test that performance is VERY poor, and at times leads the browser to become unresponsive.

Some notes about this here: https://github.com/bcgov/traction/issues/650#issuecomment-1580986419

No file, test, or specific entry point is named. Start by tracing the ledger browser's query path for filtering parameters and read the linked notes from traction#650; done should mean high-volume ledger queries no longer make the browser unresponsive.

Written by the indexing model from the issue text.