fix(case): fixing case filtering

[whitdog47]

This PR refines the apply_filter_specific_joins mapping by removing several unused case-related entries to fix case filtering behavior.

• Removed redundant CaseType, CaseSeverity, CasePriority mappings to Project
• Dropped explicit Case joins for IndividualContact, Assignee, and Project
• Kept only necessary entity-to-project relations for cleanup

[Copilot]

Pull Request Overview

This PR refines the apply_filter_specific_joins mapping by removing several unused case-related entries to fix case filtering behavior.

• Removed redundant CaseType, CaseSeverity, CasePriority mappings to Project
• Dropped explicit Case joins for IndividualContact, Assignee, and Project
• Kept only necessary entity-to-project relations for cleanup

Comments suppressed due to low confidence (3)

src/dispatch/database/service.py:463

• Removing the (CaseType, "Project") mapping means filters on case types tied to projects will no longer generate the necessary JOIN, which may break existing queries. Consider handling this relationship elsewhere or adding a fallback path.

(CaseType, "Project"): (Project, False),

src/dispatch/database/service.py:464

• Since case severity and priority mappings were removed, add or update tests to verify filtering by case severity/priority still behaves as intended or raises a clear error.

(CaseSeverity, "Project"): (Project, False),

src/dispatch/database/service.py:461

• [nitpick] It would help to document why the case-related join entries were removed (e.g., in a docstring or CHANGELOG) so future maintainers understand the intent behind this cleanup.

def apply_filter_specific_joins(model: Base, filter_spec: dict, query: orm.query):