tool to read tip of state db

[CoderZhi]

Create a tool to read tip of state db

Fixes #(issue)

Type of change

Please delete options that are not relevant.

• [] Bug fix (non-breaking change which fixes an issue)
• [] New feature (non-breaking change which adds functionality)
• [] Code refactor or improvement
• [] Breaking change (fix or feature that would cause a new or changed behavior of existing functionality)
• [] This change requires a documentation update

How Has This Been Tested?

Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration

• [] make test
• [] fullsync
• [] Other test (please specify)

Test Configuration:

• Firmware version:
• Hardware:
• Toolchain:
• SDK:

Checklist:

• [] My code follows the style guidelines of this project
• [] I have performed a self-review of my code
• [] I have commented my code, particularly in hard-to-understand areas
• [] I have made corresponding changes to the documentation
• [] My changes generate no new warnings
• [] I have added tests that prove my fix is effective or that my feature works
• [] New and existing unit tests pass locally with my changes
• [] Any dependent changes have been merged and published in downstream modules

[codecov]

Codecov Report

Merging #3659 (5afbd26) into master (e9732a1) will decrease coverage by 0.25%.
The diff coverage is 82.11%.

❗ Current head 5afbd26 differs from pull request most recent head a632409. Consider uploading reports for the commit a632409 to get more accurate results

@@            Coverage Diff             @@
##           master    #3659      +/-   ##
==========================================
- Coverage   74.95%   74.69%   -0.26%     
==========================================
  Files         269      266       -3     
  Lines       23819    23754      -65     
==========================================
- Hits        17854    17744     -110     
- Misses       5039     5083      +44     
- Partials      926      927       +1     

Impacted Files	Coverage Δ
db/config.go	100.00% <ø> (ø)
db/trie/mptrie/node.go	100.00% <ø> (ø)
ioctl/newcmd/action/action.go	79.62% <ø> (+0.09%)	⬆️
ioctl/newcmd/node/nodedelegate.go	70.19% <0.00%> (-0.95%)	⬇️
ioctl/newcmd/node/nodeprobationlist.go	90.90% <0.00%> (-4.33%)	⬇️
action/protocol/execution/evm/evm.go	44.57% <26.66%> (-0.86%)	⬇️
db/trie/mptrie/hashnode.go	36.36% <41.17%> (-54.55%)	⬇️
db/trie/mptrie/merklepatriciatrie.go	78.73% <46.80%> (-12.70%)	⬇️
db/db_bolt.go	72.13% <50.00%> (-0.39%)	⬇️
db/trie/mptrie/leafiterator.go	62.06% <50.00%> (ø)
... and 20 more

📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more

[millken]

Don't do this, DB should be opened in read-only mode
https:/etcd-io/bbolt/blob/fd5535f71f488dda0915f610b6ca8c77c9ca2c59/db.go#L223-L234

	// Lock file so that other processes using Bolt in read-write mode cannot
	// use the database  at the same time. This would cause corruption since
	// the two processes would write meta pages and free pages separately.
	// The database file is locked exclusively (only one process can grab the lock)
	// if !options.ReadOnly.
	// The database file is locked using the shared lock (more than one process may
	// hold a lock at the same time) otherwise (options.ReadOnly is set).

[sonarcloud]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

No Coverage information
0.0% Duplication

[millken]

add new func db.CreateKVStoreWithOption, and use readonly option open the DB