NIAD-3170: Set effective end date to start date in generated MedicationStatement when status is active when mapping acute plans.

[MartinWheelerMT]

What

• Add unit tests to ensure that the generated MedicationStatement has an effective.end set to the value of effective.start when the status is active and associated Order has no dispenseRequest.validityPeriod.end.
• Add unit tests to assert the current behaviour depending on the MedicationStatement.status
• Add functionality to MedicationRequestMapper for the above.
• Update integration test files to now test that the end value is correctly populated.

Why

Currently we only set effective.start value when generating a MedicationStatement whilst mapping an acute plan where multiple ehrSupplyPrescribe reference a single acute ehrSupplyAuthorise, whilst when building new MedicationStatements we also set end to the same value as start when status is active and the is not a end value provided.

This change is to ensure the functionality remains consistent.

Type of change

Please delete options that are not relevant.

• Bug fix (non-breaking change which fixes an issue)

Checklist:

• I have performed a self-review of my code
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes