feat: search for a snapshot that fulfills a queried BlockHash or TxHash

[joshieDo]

PR into #5287

There are some changes to accomplish what the title says.

• Snapshot file name now has transaction range as well. This helps in creating two inner indexes (BlockNumber -> Range<TxNumber> & TxNumber -> Range<BlockNumber>), where each key is the end number of a snapshot segment.
• The above indexes are calculated when SnapshotProvider is created and read from disk. This enables handling custom range snapshots instead of being tied to the default one.
  • Given that, two functions were introduced: get_segment_provider_from_transaction and get_segment_provider_from_block
• Adds SnapshotProvider::find_snapshot. This will iterate all existing snapshots (loading them from disk into the dashmap,) until we find one that returns Some(T). Example:

    fn header_td(&self, block_hash: &BlockHash) -> RethResult<Option<U256>> {
        self.find_snapshot(SnapshotSegment::Headers, |jar_provider| {
            Ok(jar_provider
                .cursor()?
                .get_two::<HeaderMask<CompactU256, BlockHash>>(block_hash.into())?
                .and_then(|(td, hash)| (&hash == block_hash).then_some(td.0)))
        })

• Uses above to implement some more provider functions to SnapshotsProvider

[mattsse]

lgtm

[shekhirin]

Suggested change

	path.file_name().ok_or_else(|| ProviderError::MissingSnapshot)?,
	path.file_name().ok_or_else(|| ProviderError::MissingSnapshot(segment, path))?,

[joshieDo]

ended up creating more variants

[shekhirin]

can we add a comment here why it's correct to do unwrap_or(0) and always return a range on latest snapshot?