Currently, when a testCase is deleted, there is a risk that its associated testCaseResolutionStatus records remain in the entity_relationship table as orphaned entries. While the Data Retention App successfully clears out standard Entity relationships during deletion, it needs to be updated to explicitly handle these incident statuses.

Context
testCaseResolutionStatus entries (which track incident events like New, Acknowledged, Assigned, Resolved) are mapped to their parent testCase via the entity_relationship table.

Over time, if these relationships are not cleaned up when the parent test case is removed, it could lead to unnecessary database bloat and lingering orphaned data.

Proposed Solution / Acceptance Criteria
[ ] Update the Data Retention App / cleanup logic to ensure it identifies and deletes any testCaseResolutionStatus mapping entries in the entity_relationship table when the associated parent testCase is deleted.

[ ] Ensure the cleanup does not inadvertently affect the historical time-series data (test_case_resolution_status_time_series) unless specifically dictated by retention policies.