Katana forking tracking

[kariy]

right now we're lacking tests on katana's forking feature. not much tests have been written for the forked storage provider.

the flow of the forked storage provider should generally be:

1. try to get the requested data from local storage
2. if not found, request from remote network
3. cache the result and return the value

need to write tests that ensure these steps are done correctly.

Tasks

Beta Give feedback

1. better traces
2. add metrics
3. test if the caching system works
4. ensure 'not yet fetched' vs 'default' value is handled correctly ref fix(katana-provider): temporarily invalidate cache if nonce or class hash is default value #1850

[ScottyDavies]

hello @glihm can i hop on this?