Implement changes to REST functionality

[chris-kuryak]

Problem statement

REST does not currently have the ability to send "keys" in the body of the message (for ELIMS) and ability to authenticate with JKS certificates (for CA).

What you need to know

ELIMS requires we send shared key in the body of the message and doesn't need any other other form of authentication. ELIMS implementation guide: ELIMS WebServicesHub API Integration Guide.docx

CA only requires that we only authenticate via JKS certificate no other form of authentication is necessary.

Our REST transport currently assumes OAuth is needed for all receivers. We need to re-work that logic to only do OAuth when necessary.

Acceptance Criteria

• [x] ReportStream can send keys in body of the message via RestTransport

• [x] ReportStream can authenticate using JKS certificate

• [x] Documentation is updated on how to create credentials for these new types of authentication

• [x] Ensure changes don't break existing REST receivers

• Blocking #14170 #14108

[chris-kuryak]

Blocking #14170 #14108

[chris-kuryak]

Victor will pair with Lucero on this before we kick off Michigan

[chris-kuryak]

Waiting for CDC to add ELIMS whitelisting and CA Certificate through DevOps

[chris-kuryak]

Depending on if the CA and ELIMS tickets are unblocked, this one will also be unblocked. Lucero and Victor to confirm.