[Part 2 / Phase 10] PathogenClassification: DTO/Entity wiring

[roldy]

Problem Description

Context

Part of Epic: [Epic] PathogenClassification: Replace GenoTypeResult & SeroGroupSpecification enums
Blocked by: Phases 8 & 9

Wire the new pathogenClassification field through PathogenTestDto, PathogenTest,
CaseDataDto, Case, and the facade EJBs. Add case write-back on positive genotyping/serogrouping save.

Proposed Solution

Tasks

• PathogenTestDto.java — remove genoTypeResult, genoTypeResultText, seroGroupSpecification, seroGroupSpecificationText; add pathogenClassification + pathogenClassificationDetails; add constant strings PATHOGEN_CLASSIFICATION, PATHOGEN_CLASSIFICATION_DETAILS
• PathogenTest.java — same field removals/additions; add @ManyToOne FK mapping for pathogenclassification_id
• PathogenTestFacadeEjb.java — update DTO↔entity mapping; add case write-back: when test type is GENOTYPING or SEROGROUPING and result is POSITIVE, write pathogenClassification to the associated case
• CaseDataDto.java — add pathogenClassification reference field alongside diseaseVariant
• Case.java — add pathogenClassification FK field
• CaseDataFacadeEjb.java — map pathogenClassification to/from case entity

Additional Information

Acceptance Criteria

• mvn compile -pl sormas-api,sormas-backend passes
• Saving a MEASLES GENOTYPING + POSITIVE pathogen test writes pathogenClassification to the case
• Existing diseaseVariant / rsvSubtype / testedDiseaseVariant fields are untouched