[prathshenoy]

Summary

What:

• Add an issue-tracking controller that opens reported issues and closes missing issues when a build is finalized.
• Process issues in small batches, resume saved work, and ignore outdated notifications without enabling the consumer yet.

Why:

• Turn persisted build issues into current issue state without trying to process an entire queue in one delivery. Large issue sets may take longer than a delivery allows, so each pass handles a bounded batch and saves its position before requesting another delivery. The next pass resumes the planned change and scan instead of starting over.
• Keep delayed messages from undoing newer issue state. A newer notification first finishes any saved work, then checks whether its build is still eligible to update the queue. Refreshes open reported issues without closing missing ones; finalization also closes issues absent from the build’s accumulated failures, except when the build was canceled and validation may not have run.

Test Plan

• Add unit tests.
• Verify chunk continuation and stale-worker rejection with two real consumers, forced partition takeover, and MySQL-backed state and history.

Revert Plan

• Revert dependents first, then this PR. No runtime consumer is enabled; the planned-change application and storage layers remain in place.

Issue Links

• CODEM-607

Stack

1. feat(stovepipe): Retain versioned issue state #942
2. feat(stovepipe): Save planned issue changes #943
3. feat(stovepipe): Apply planned issue changes #932
4. feat(stovepipe): Track issues in bounded passes #940
5. feat(stovepipe): Publish issue-tracking updates #939