Add optional traversal limit for commit offset lookup

[NssGourav]

Summary

• Add a new polaris.persistence.commit-offset-lookup-max-traversal parameter (default 0 = unlimited) to optionally bound commit history traversal while resolving offsets.
• Enforce the limit in CommitsImpl.commitLog() and CommitsImpl.commitLogReversed() during offset lookup, failing fast with a clear exception when exceeded.
• Add tests covering the fail-fast behavior for both variants.

Rationale

CommitsImpl currently walks commit history unbounded when resolving offsets. In pathological cases (very large histories or missing/far-back offsets) this can lead to unbounded work.

The safeguard is opt-in (default unlimited) to avoid breaking background/maintenance flows that may legitimately traverse the full log.

Test plan

• ./gradlew :persistence:nosql:persistence-impl:test

Fixes #4000

[Subham-KRLX]

A few things worth addressing like the limit is still inside CommitsImpl, but @snazy mentioned the TODO was meant for the call sites (REST/service layer), not the implementation itself worth clarifying with him before going further. There's also a counter bug where commitLog and commitLogReversed count traversals differently since traversed starts at 0 in one and 1 in the other, so the same maxTraversal value behaves inconsistently. On the exception side, IllegalStateException feels off for an expected operational limit a dedicated exception would be easier to catch specifically. For the tests, the .hasNext() in the commitLog test is misleading since the exception fires during the commitLog() call itself, not lazily, and there's also no test for the success case where the offset is found within the limit. Overall the approach is reasonable, just needs a quick sync with the maintainer on the architectural question first.

[NssGourav]

Thanks agreed on the feedback.

I understand the TODOs may be intended for call-site guardrails; I implemented an opt-in safeguard in CommitsImpl (commit-offset-lookup-max-traversal, default 0 = unlimited) to avoid impacting maintenance flows unless configured.

Fixed traversal counting so commitLog and commitLogReversed behave consistently.
Replaced IllegalStateException with CommitOffsetTraversalLimitExceededException for easier catching.

Updated tests to assert at the right point and added success path coverage.