test(zone): cover configurable batch anchor stepping

[mattsse]

Summary

• Add BatchAnchorConfig so the batch submitter can use the production EIP-2935 window by default while integration tests can shrink the window to a few blocks.
• Thread the anchor config through the sequencer, zone monitor, CLI defaults, and integration test helper.
• Keep ancestry submissions on the recent-anchor path while leaving verifier config and proof bytes empty until real proof generation is implemented.
• Keep the long ignored extended-gap test, and add fast configured-window stepping tests that verify ancestry calldata and multiple stepping batch submissions.

Why

The existing ignored extended-gap test needs thousands of L1 blocks before it can exercise the out-of-window path. Configurable limits let the same behavior run with a 10-block test window, making the stepping and ancestry paths practical to cover in regular integration tests.