fix(drive): merk caching in contract caching (irony)

[QuantumExplorer]

Issue being fixed or feature implemented

Merk caching was causing a problem. The returned cost operation might use the cache, and this cache might cause the cost to be lower if we are using transactions and the item was just inserted. Because contracts would be added to the cache on insert this was the case. Fetching them from disk was less expensive. When the node would come back online and fetch it again the cost would differ between nodes causing a source of non determinism.

What was done?

In order to fix this we allow querying without the Merk cache. While this might not have been strictly needed, it was also a good improvement for many query methods when proofs are not needed.

How Has This Been Tested?

Breaking Changes

Checklist:

• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have added or updated relevant unit/integration/functional/e2e tests
• I have made corresponding changes to the documentation

For repository code-owners and collaborators only

• I have assigned this pull request to a milestone