refactor: consolidate datastore and burn datastore data

[hugocaillard]

fix: #1540

Description

The simnet memory datastore was only able to store blocks data for pre-nakamoto blocks (with 1 stacks block per burn block).
With this refactor, we now handle multiple stacks-block per burn block.

• The Datastore becomes ClarityDatastore and holds the key/value store for Clarity data.
• The BurnDatastore becomes the Datastore and holds all of the stacks block and burn blocks data
• BlockInfo has been removed in favor of BurnBlockInfo and StacksBlockInfo

[codecov]

Codecov Report

Attention: Patch coverage is 83.41969% with 96 lines in your changes missing coverage. Please review.

Files with missing lines	Patch %	Lines
components/clarity-repl/src/repl/datastore.rs	73.82%	78 Missing ⚠️
components/clarity-repl/src/repl/interpreter.rs	94.02%	11 Missing ⚠️
components/clarity-repl/src/repl/session.rs	93.65%	4 Missing ⚠️
components/clarinet-cli/src/frontend/cli.rs	0.00%	1 Missing ⚠️
components/clarity-events/src/bin.rs	0.00%	1 Missing ⚠️
components/clarity-repl/src/repl/clarity_values.rs	96.87%	1 Missing ⚠️

📢 Thoughts on this report? Let us know!

[tippenein]

I like where this is going. Was this in relation to some issue or just a cleanup?

[hugocaillard]

@tippenein
Thx!
This is to address an actual issue, but ended up being a way bigger refactor than I expected.

Basically we went realistc block times in simnet between burn blocks and between stacks blocks. We were only tracking one type of blocks so far (doesn't really matter which type, since we had a 1:1 relation between burn and stacks blocks).
So now we store burn_blocks and stacks_blocks, and we store realistic times for both.
The clarity_datastore basically only holds the MARF keys and values now, and the datastore stores burn and stacks blocks.
We know also have burn_block_info and stacks_block_info

[krl]

looks good

[csgui]

I verified the datastore changes, and they seem to be ok. I added some remarks that could be improved, if applicable.

[csgui]

Changes on datastore LGTM!