Analysis of behavior of UpdateTrackingAccount.getStorageValue to rework it to hit RocksDB cache more often and avoid duplicated retrievals.

[non-fungible-nelson]

Description

As a user, I want to have less IO on the database to keep performance open for other operations when using the getStorageValue method in UpdateTrackingAccount.

Acceptance Criteria

• The cache is hit only once if I need to read a storage value that is not being updated. I would like to use the cache for storage that is being updated as well but it is not as important.

This issue is to track an analysis for future performance improvements. This issue is not a bug but area of improvement.