#20680)

Add `--integrity.budget <duration>` to `erigon seg integrity` that caps
total wall-clock time for an integrity run.

- When set, checks are sorted cheap → heavy (based on
`integrity.FastChecks` order) and each receives a per-check deadline of
`remaining / remaining_checks`, so finishing early on a cheap check
rolls budget forward to the heavy tail.
- On per-check timeout: log `[integrity] budget exhausted, moving on` at
INFO and continue to the next check. Not treated as an integrity failure
— `--failFast` only reacts to actual integrity errors.
- When not set (default): no change in behavior — user-supplied order
preserved, no deadline applied.
- `BlockReader.IntegrityTxnID` now takes `ctx` and polls every 1000
segments so `BlocksTxnID` honors the budget.
- `CheckKvi` producer now checks `ctx` every 100k keys, so skip-heavy
runs (e.g. `CommitmentKvi` with `SampleRatio=0`) don't overshoot their
slice by minutes.
- `doPublishable` takes `datadir.Dirs` directly instead of
`*cli.Context`.

follow up:
- pick to release/3.4
- change automation script to allot 30min budget

---------

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

…#20835)

## Summary

`seg integrity` runs `CommitmentHistVal` and `StateRootVerifyByHistory`
regardless of whether commitment history is persisted on the datadir.
Both depend on commitment history `.v` files:

- `CheckCommitmentHistVal` iterates `.v` files; when none exist it
returns nil after logging `files=0`, which silently masks
misconfiguration as a passing check.
- `CheckCommitmentHistAtBlkRange` would fail confusingly when trying to
read history that isn't there.

This PR reads `rawdb.ReadDBCommitmentHistoryEnabled` once at the start
of `doIntegrity` and skips both checks with an informative log line when
the flag is off. Mirrors the existing `BorEvents` / `BorSpans`
chain-guard pattern in the same dispatch switch.

The other commitment checks (`CommitmentRoot`, `CommitmentKvi`,
`CommitmentKvDeref`, `StateVerify`) operate on the domain `.kv` files
and don't depend on history, so they remain unconditional.

## Test plan

- [x] `make lint` clean
- [x] `go build ./cmd/utils/app/...` succeeds
- [x] On a no-history datadir, run `seg integrity --check
CommitmentHistVal` and confirm the skip log appears and the command
exits 0 instead of "passing" with files=0
- [x] On a history-enabled datadir, confirm `CommitmentHistVal` and
`StateRootVerifyByHistory` still execute as before