[prathshenoy]

Summary

What:

• Add paginated request-level issue lookups with new, existing, and closed classifications.
• Report whether results are in progress, complete, incomplete, or unavailable.

Why:

• Let consumers explain which issues a request introduced, encountered, or closed without reconstructing that history from the queue's current state.
• Make partial and unavailable results explicit so an empty response is not mistaken for a clean request. Completed request results remain independent of later issue changes.

Test Plan

• Add unit tests.
• Verify materialized results, pagination, and completion status through the running service.

Revert Plan

• Revert this PR. Recording continues independently, and the stored results remain available for a later reader.

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