[prathshenoy]

Summary

What:

• Add paginated storage for request-level issue summaries.
• Support conditional updates as a request's issue results advance.

Why:

• Provide an efficient way to list what a request introduced, encountered, or closed. Existing issue history is organized by issue rather than request, so reconstructing each request's results on every read would require scanning unrelated history.
• Allow the materializer to retain a closure when an older opening or report is replayed later. Version-guarded replacements support that ordering without a transaction.

Test Plan

• Add unit tests.
• Verify storage and conditional updates against a real database.

Revert Plan

• Revert dependent readers and materialization first, then this PR. The unused summary table can remain.

Issue Links

• CODEM-607

Stack

1. feat(stovepipe): Store request issue summaries #1023
2. feat(stovepipe): Retain repeat issue reports #1027
3. feat(stovepipe): Materialize request issue results #1024
4. feat(stovepipe): Add request issue lookups #1025