Write request and response handling functions for message parser payloads

[bamader]

No description provided.

[bamader]

As part of the orchestration overhaul, each of the services connected to the orchestration container (validation, convert to fhir, ingestion, message parsing, save to DB) needs a function that not only composes appropriate input to send to the API, but unpacks response output for processing in the next service. Right now, we have a relatively uncontrolled data flow of kwargs, globals, and other hard to grok code, so the scope of this ticket is to right new, modular, decomposed I/O methods responsible for working with the message parser service.

Acceptance Criteria:

• A function build_message_parser_request is written which takes as input the general model of the orchestration service and formulates it as a dictionary whose K-V pairs match the model input of the message parser service (which is dependent on the endpoint being hit)
• A function unpack_message_parser_response is written which takes as input the response object of the message parser service, checks its status code (returning an error if the code isn't 200), and returns data/information in general form so that the next service call, whatever it might be, can atomically use the information without coupling.