feat(provider): consistent database view

[rkrasiuk]

Description

Extracted from #6576 and modified.

This PR adds an ability to create a consistent view of the database. Each attempt to create a provider will be followed by tip consistency checks.

Intended Usage

This view is useful when attempting to perform parallel reads of the state across multiple threads while preserving the guarantee that the state remains unchanged.

[gakonst]

@mattsse ptal

[gakonst]

had some time to review, simple enough. I think the mevoors like Snoopy may want this too

[mattsse]

I think this makes sense,
but this is really enforces consistent Tip, so view sounds a bit too general to me

wdyt @shekhirin

[rkrasiuk]

imo it's fine to call it a view as it gets invalidated on chain advancement

[shekhirin]

LGTM. Do I understand correctly that this is just a precautionary measure in an already consistent scenario (trie update), when we're already sure there are no other write transactions happening during that time? Not fully understand what will happen if this doesn't hold, do we just crash?

[shekhirin]

I think this makes sense, but this is really enforces consistent Tip, so view sounds a bit too general to me

wdyt @shekhirin

agreed it's fine to call it a view, although can add it to comments why so: because all updates are atomic, and the tip changes at the same time as other parts of the database.

[rkrasiuk]

@shekhirin this is a pre-cautionary measure against the misuse of the parallel/async API. if we misuse it internally, ye we should crash because our logic is flawed. for external use it's handy to catch that error and decide what to do next