Engagement/jessica/15541 cli add code to condition

[JessicaWNava]

This PR adds code to condition code to the fhirdata command.

Test Steps:

1. Run something like the following to see that the SNOMED code is added to the output bundle:
   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-output.fhir --output-format FHIR -s classpath:/metadata/fhir_transforms/senders/SimpleReport/simple-report-sender-transform.yml -r classpath:/metadata/hl7_mapping/receivers/STLTs/ME/ME-receiver-transform.yml

Changes

• adds code to condition code 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 19s ⏱️ +7s
  161 suites ±0       4 💤 ±0 
  161 files   ±0       0 ❌ ±0 

Results for commit 6a73ba9. ± Comparison against base commit 93c0b4f.

♻️ This comment has been updated with latest results.

[github-actions]

Integration Test Results

 53 files   53 suites   28m 35s ⏱️
409 tests 400 ✅ 9 💤 0 ❌
412 runs  403 ✅ 9 💤 0 ❌

Results for commit 6a73ba9.

♻️ This comment has been updated with latest results.

[sonarqubecloud]

Quality Gate failed

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

See analysis details on SonarCloud