Cherry-pick of #20722 to release/3.4.

…21103)

- This reverts commit 91088e6.
- we need to regenerate receipts before re-adding this check back.
- should fix:

```
INFO[05-08|23:29:49.236] adjusting receipt current version to v1.1
EROR[05-08|23:29:49.476] Snapshot file is newer than this Erigon build supports: file=v3.0-receipt.187416-187420.v, highest_supported=<v3.0. To fix, either upgrade Erigon to a newer release, or align snapshots by command: `erigon snapshots reset --datadir $DATADIR --chain $CHAIN`
panic: Snapshot file is newer than this Erigon build supports: file=v3.0-receipt.187416-187420.v, highest_supported=<v3.0. To fix, either upgrade Erigon to a newer release, or align snapshots by command: `erigon snapshots reset --datadir $DATADIR --chain $CHAIN`

goroutine 136 [running]:
github.com/erigontech/erigon/db/version.Versions.MustSupport({{0x1, 0x1}, {0x1, 0x0}}, {0x3, 0x0}, {0xc001c91edf, 0x1c})
        
```

- added issue for adding this check back -
#21104

Fixes erigontech#20560.

Problem: 
bloatnet 3B keys .efi file building: FuseFIlter used `t2hash=29GB` and
`reverseOrder=26GB`
we can't mmap FuseFilter without forking it. But maybe it's okey. Maybe
it's better to shard FuseFilter rather than mmap large thing. Maybe
sharding will improve data-locality.

--
Solution: 
shard `fusefilter` by first byte of `keyHash`. it will reduce building
allocation buffers 256x times. And it will not add reading overhead.
(`keyHash>>56` is not same as `byte(keyHash)`. it's `hi/lo` bytes.)

- Writer: re-using 1 `xorfilter.BuildBinaryFuse` to build all shards
- `ShardedReader` is a `[256]Reader`. Lookup:
`shards[keyHash>>56].ContainsHash(hash)`

Depends on: erigontech#20722

---------

Co-authored-by: JkLondon <me@ilyamikheev.com>

Fixes #20560.

Problem: 
bloatnet 3B keys .efi file building: FuseFIlter used `t2hash=29GB` and
`reverseOrder=26GB`
we can't mmap FuseFilter without forking it. But maybe it's okey. Maybe
it's better to shard FuseFilter rather than mmap large thing. Maybe
sharding will improve data-locality.

--
Solution: 
shard `fusefilter` by first byte of `keyHash`. it will reduce building
allocation buffers 256x times. And it will not add reading overhead.
(`keyHash>>56` is not same as `byte(keyHash)`. it's `hi/lo` bytes.)

- Writer: re-using 1 `xorfilter.BuildBinaryFuse` to build all shards
- `ShardedReader` is a `[256]Reader`. Lookup:
`shards[keyHash>>56].ContainsHash(hash)`

Depends on: #20722

---------

Co-authored-by: JkLondon <me@ilyamikheev.com>

Cherry-pick of
[be36d4f](be36d4f)
(original PR #20644) onto `performance`.

## Summary
- Shards `fusefilter` by `keyHash>>56` (256 shards) to cut FuseFilter
build-time RAM ~256× on large `.efi` files (3B-key bloatnet case).
- Writer reuses one `xorfilter.BuildBinaryFuse` to build all shards;
`ShardedReader` is a `[256]Reader` with lookup
`shards[keyHash>>56].ContainsHash(hash)`.
- Adds `ExistenceFilterVersion = 2` (sharded format), keeps v1
(monolithic) and v0 (legacy) intact. `recsplit.RecSplitArgs.Version` is
now `version.DataStructureVersion` (was `uint8`).
- Wires `snaptype.BuildIndex` to pick `recsplit.ExistenceFilterVersion`
whenever the index version is not `v1.0` (v1.0 keeps inner v=0 for
compat).
- Brings the full new test set: sharded writer/reader tests, corruption
tests, fuzz tests, real-file tests, and benchmarks +
`scripts/fusefilter-bench/`.

## Cherry-pick status
Clean cherry-pick. No manual conflict resolutions required —
`performance` already has all the prerequisites the original commit
assumed:
- `xorfilter v0.5.1` (provides `MakeBinaryFuseBuilder` /
`BuildBinaryFuse`)
- Package-scope `headerSize` in
`db/datastruct/fusefilter/fusefilter_reader.go`
- `offsetFile *os.File` / `offsetWriter *bufio.Writer` in
`recsplit.RecSplit` (from PR #20722)

Auto-merge handled minor textual deltas in `.gitignore`,
`fusefilter_reader.go`, `recsplit/index.go`, and `db/state/domain.go`
without conflicts.

## Test plan
- [ ] `go build` of affected packages: passes locally
(`db/recsplit/...`, `db/datastruct/fusefilter/...`, `db/snaptype/...`)
- [ ] `go test ./db/datastruct/fusefilter/... ./db/recsplit/...`
- [ ] CI on the branch

> Note: `./db/state/statecfg/...` fails to build with `undefined:
InitSchemas` on `origin/performance` independently of this PR —
pre-existing issue on the base branch, unrelated to the cherry-pick.

## References
- Original PR: #20644
- Original issue: #20560

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-authored-by: Alex Sharov <AskAlexSharov@gmail.com>
Co-authored-by: JkLondon <me@ilyamikheev.com>