[prathshenoy]

Summary

What:

• Extend issue history to retain repeat reports and original opening references.
• Keep repeat reports from changing lifecycle status or transition timestamps.

Why:

• Retain evidence that later validation builds encountered an already-open issue. Those reports are needed for request-level existing results, but must not reopen an issue or move its transition timestamp.
• Preserve the opening in each new event so replay can identify the occurrence after the issue has closed or reopened. Deploy the additive history column before updated consumers; existing lifecycle history remains readable without backfilling it.

Test Plan

• Add unit tests.
• Verify event retention and queue isolation against a real database.

Revert Plan

• Revert dependent reporting and projection changes first, then this PR. Retained repeat-report events and the additive column can remain unused.

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