Engagement/jessica/15540 fhirdata specify receiver

[JessicaWNava]

This PR adds the ability to specify a receiver on the fhirdata command so that their settings can be applied.

Test Steps:

1. Choose a message that one of the following settings would make a change to:
   truncateHDNamespaceIds,truncateHl7Fields,convertTimestampToDateTime,convertPositiveDateTimeOffsetToNegative,convertDateTimesToReceiverLocalTime,useHighPrecisionHeaderDateTimeFormat,timeZone
2. Run the fhirdata command on it example command:
   fhirdata -i /Users/jessicawillis/git/newnew/prime-reportstream/prime-router/src/testIntegration/resources/datatests/FHIR_to_HL7/sample_ME_20240806-0001.fhir -o /Users/jessicawillis/git/newnew/prime-reportstream/prime-router/src/testIntegration/resources/datatests/FHIR_to_HL7/sample_ME_20240806-0001.hl7 --output-format HL7 -r classpath:/metadata/hl7_mapping/receivers/STLTs/ME/ME-receiver-transform.yml -s classpath:/metadata/fhir_transforms/senders/SimpleReport/simple-report-sender-transform.yml --receiver-name full-elr --org mo-phd --receiver-setting-env staging
3. Check the changes were made in the output file.

Changes

• added params to the fhirdata command.

Checklist

Testing

• Tested locally?
• Ran ./prime test or ./gradlew testSmoke against local Docker ReportStream container?
• (For Changes to /frontend-react/...) Ran npm run lint:write?
• Added tests?

Process

• Are there licensing issues with any new dependencies introduced?
• Includes a summary of what a code reviewer should test/verify?
• Updated the release notes?
• Database changes are submitted as a separate PR?
• DevOps team has been notified if PR requires ops support?

Linked Issues

• Fixes #issue

To Be Done

Create GitHub issues to track the work remaining, if any

• #issue

Specific Security-related subjects a reviewer should pay specific attention to

• Does this PR introduce new endpoints?
  • new endpoint A
  • new endpoint B
• Does this PR include changes in authentication and/or authorization of existing endpoints?
• Does this change introduce new dependencies that need vetting?
• Does this change require changes to our infrastructure?
• Does logging contain sensitive data?
• Does this PR include or remove any sensitive information itself?

If you answered 'yes' to any of the questions above, conduct a detailed Review that addresses at least:

• What are the potential security threats and mitigations? Please list the STRIDE threats and how they are mitigated
  • Spoofing (faking authenticity)
    • Threat T, which could be achieved by A, is mitigated by M
  • Tampering (influence or sabotage the integrity of information, data, or system)
  • Repudiation (the ability to dispute the origin or originator of an action)
  • Information disclosure (data made available to entities who should not have it)
  • Denial of service (make a resource unavailable)
  • Elevation of Privilege (reduce restrictions that apply or gain privileges one should not have)
• Have you ensured logging does not contain sensitive data?
• Have you received any additional approvals needed for this change?

[github-actions]

Dependency Review

✅ No vulnerabilities or license issues or OpenSSF Scorecard issues found.

OpenSSF Scorecard

Package	Version	Score	Details

Scanned Manifest Files

[github-actions]

Test Results

1 229 tests  ±0   1 225 ✅ ±0   7m 13s ⏱️ ±0s
  161 suites ±0       4 💤 ±0 
  161 files   ±0       0 ❌ ±0 

Results for commit 69d1de5. ± Comparison against base commit 372c5fb.

♻️ This comment has been updated with latest results.

[github-actions]

Integration Test Results

 53 files  ±0   53 suites  ±0   28m 3s ⏱️ +7s
410 tests ±0  401 ✅ ±0  9 💤 ±0  0 ❌ ±0 
413 runs  ±0  404 ✅ ±0  9 💤 ±0  0 ❌ ±0 

Results for commit 69d1de5. ± Comparison against base commit 372c5fb.

♻️ This comment has been updated with latest results.

[sonarcloud]

Quality Gate failed

Failed conditions
0.0% Coverage on New Code (required ≥ 80%)

See analysis details on SonarCloud