1727 - Improve Tx queries performance

[Cmdv]

Description

This fixes #1727

TODO:

• [x] add to CacheStatus
• [x] Check the cache before making the query unless cache not active
• [x] maybe change to use an LRU cache
• [ ] Populate the cache right after inserting TX

Checklist

• [ ] Commit sequence broadly makes sense
• [ ] Commits have useful messages
• [ ] New tests are added if needed and existing tests are updated
• [ ] Any changes are noted in the changelog
• [ ] Code is formatted with fourmolu on version 0.10.1.0 (which can be run with scripts/fourmolize.sh)
• [ ] Self-reviewed the diff

Migrations

• [ ] The pr causes a breaking change of type a,b or c
• [ ] If there is a breaking change, the pr includes a database migration and/or a fix process for old values, so that upgrade is possible
• [ ] Resyncing and running the migrations provided will result in the same database semantically

If there is a breaking change, especially a big one, please add a justification here. Please elaborate more what the migration achieves, what it cannot achieve or why a migration is not possible.

[kderme]

Any ideas on how the eviction of old data will work?

[Cmdv]

@kderme I'm making it an LRU so they'll just get pushed out if they haven't gotten used. Will be easier than trying to work out when a TxId in the cache should be deleted.

[kderme]

We should somehow handle rollbacks, since tx table is deleted on rollbacks. I think we can follow a very simple approach, simply delete the whole TxCache when there is a rollback, as part of rollbackCache.