Update Lineage Tracking in FHIRReceiver Function

[arnejduranovic]

User Story

As the owner of the ReportStream Architecture,
I want the FHIRReceiver pipeline step to implement lineage tracking correctly,
so that FHIRReceiver behaves the same as other UP steps in this regard.

Description/Use Case

CONTEXT: Ticket #16011 was created following the initial FHIRReceiver implementation and the QueueMessage followup to rethink how the "submission specific" events should be designed. Upon further investigation, it has been decided Ticket #16011 should be closed and instead the FHIRReceiver should be updated so that a new event is not required. The initial implementation deviated from the normal report and lineage creation/handling and should be brought back in line. Once this is done, the submission specific events can go away and reuse the currently existing Report events.

The goal of this ticket is to:

• Create an empty report with child lineage when there is a processing error (everywhere there is sendSubmissionProcessingError currently in FHIRReceiver)
• sendSubmissionProcessingError should be removed entirely and replaced with sendReportProcessingError
• verify kdoc of getSender is correct for "The sender, or null if the sender was not found or is inactive." and update the else block to match

Risks/Impacts/Considerations

Dev Notes

Acceptance Criteria

• FHIRReceiver creates an empty report when an error is encountered
• Events updated accordingly

[MichaelEsuruoso]

Hey team! Please add your planning poker estimate with Zenhub @adegolier @arnejduranovic @david-navapbc @jack-h-wang @jalbinson @JFisk42 @kant777 @mkalish @thetaurean