Create State implementation with registering all of the specific ReadableKVStates

[bilyana-gospodinova]

Description:
This PR adds a MirrorNodeState class that implements the State interface. The class registers all of needed readable and writable states. Each service (TokenService, ContractService or FileService) needs a different set of states in order to function properly. The readable states are initialised only once and are singleton instances and will be used by all of the threads. They are the implementations of all of the ReadableKVStates. For the writable states we need only 1 facade implementation since no actual changes will be persisted from the memory. The writable state uses a readable state for the read operations and the modifications are kept in memory and discarded at the end of the transaction execution.

Fixes #9259

[codecov]

Codecov Report

Attention: Patch coverage is 95.53571% with 10 lines in your changes missing coverage. Please review.

Project coverage is 92.25%. Comparing base (e179868) to head (b724cbb).
Report is 5 commits behind head on main.

Files with missing lines	Patch %	Lines
.../com/hedera/mirror/web3/state/MirrorNodeState.java	90.99%	0 Missing and 10 partials ⚠️

Additional details and impacted files

@@             Coverage Diff              @@
##               main    #9700      +/-   ##
============================================
+ Coverage     92.23%   92.25%   +0.02%     
- Complexity     7628     7739     +111     
============================================
  Files           937      945       +8     
  Lines         32119    32343     +224     
  Branches       4071     4105      +34     
============================================
+ Hits          29624    29838     +214     
  Misses         1542     1542              
- Partials        953      963      +10     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[IvanKavaldzhiev]

At first glance the PR looks reasonable and have all of the needed state core components. The state should be utilized via integration tests (added in separate PR/PRs) to validate the correctness and consistency of the state. A lot of pitfalls or little issues can be missed without running actual transactions against this state. So I think this PR can be merged in this form and if it needs some touch ups - they can be made in separate PRs.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
1.6% Duplication on New Code

See analysis details on SonarQube Cloud

[steven-sheehy]

Mostly just questions

[steven-sheehy]

How would one disregard the backing map? It's required and will throw a NPE if not supplied

[bilyana-gospodinova]

It seems that code was updated but the comment was not. I will update it, thanks.

[steven-sheehy]

Will this cause a commit to flush the readable state and cause it to get re-created for every request?

[bilyana-gospodinova]

Yes, it will. I tested it without the runnable and it seems to work fine for 1 request. This was added in the example code probably for a reason. I will remove it for now and we will investigate the behaviour on parallel requests later.