16148: update FHIR reciever logic to be simpler

[mkalish]

This PR simplifies the FHIR receiver and removes the few bugs in sender parsing and event tracking. The simplification can be done because the FHIR Converter handles the same cases more robustly

Test Steps:

1. Turn on the submissions service and reportstream
2. Send a report to submissions
3. Verify it gets picked up by report stream

Changes

• Drops event handling for errors in favor of putting messages on to the queue directly
• Removes the functionality duplicated with FHIR converter

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

• Update Lineage Tracking in FHIRReceiver Function #16148

To Be Done

TBD: but there might be another follow up ticket to address this more efficiently and remove the FHIR Receiver step, but it would require some updates to the how the item lineage works

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

[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 246 tests   - 5   1 242 ✅  - 5   7m 32s ⏱️ +9s
  164 suites ±0       4 💤 ±0 
  164 files   ±0       0 ❌ ±0 

Results for commit b71dca1. ± Comparison against base commit 7c97376.

This pull request removes 5 tests.

gov.cdc.prime.router.fhirengine.azure.FHIRReceiverIntegrationTests ‑ should handle inactive sender gracefully()
gov.cdc.prime.router.fhirengine.azure.FHIRReceiverIntegrationTests ‑ test process CSV message()
gov.cdc.prime.router.fhirengine.azure.FHIRReceiverIntegrationTests ‑ test process invalid FHIR message()
gov.cdc.prime.router.fhirengine.azure.FHIRReceiverIntegrationTests ‑ test process invalid HL7 message()
gov.cdc.prime.router.fhirengine.engine.FHIRReceiverTest ‑ test handle inactive sender()

[sonarcloud]

Quality Gate passed

Issues
1 New issue
0 Accepted issues

Measures
0 Security Hotspots
96.6% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarCloud

[github-actions]

Integration Test Results

 53 files   53 suites   28m 59s ⏱️
411 tests 402 ✅ 9 💤 0 ❌
414 runs  405 ✅ 9 💤 0 ❌

Results for commit b71dca1.

[mkalish]

This didn't align with how the other reports were going to work and likely would have led to confusion as this was inverting parameters compared to other builders

[mkalish]

Rather than emit an event, we're now adding an item to the poison queue which will cause an alert and enables the engagement team to fix the configuration and requeue the message.

[mkalish]

Dropped this since the UP via the ReportFunction silently just drops a message. I'm of the opinion that if a sender is not suppose to sending reports we should revoke there access rather than have a flag that gets checked so late in the process.

[mkalish]

This checking is robustly handled in the convert step and does not need to be duplicated here.