Find a way to conduct an integration test of the `fhir-converter` where we are not introducing any **new** errors

[robertmitchellv]

What needs to be done

Given that there is FHIR validation work being done on the output of the fhir-converter and that it may take some cycles to complete, it would be great to have an integration test that would, at the very least, prevent us from introducing any new bugs.

Why it needs to be done

To stop the introduction of things that need to be fixed that are producing errors. This way we can have a fixed number to work through and hopefully achieve our goals faster.

Acceptance Criteria

List out all expected functionality/requirements

• a specific eICR and RR pair is run through the fhir-converter from main and from the feature branch t
• the output is validated using the FHIR validator
• a check is performed to ensure that the number of errors isn't going up