Update UP Convert Step to support new Secure Upload API

[arnejduranovic]

User Story

As a stakeholder of ReportStream, I want the Convert service to handle the new Upload API alongside the "reports" and "waters" apis, so that the new upload API can be used by new clients and the other clients are supported until they are migrated.

Description/Use Case

Presently, ReportStream has two upload APIs that the Convert step is currently supporting:

• "reports API" - uses Azure Functions Key Auth
• "Waters API" - uses OAuth2.0 with homemade custom Authorization server embedded in the application

The convert step should be updated to support the new UP Upload API alongside the two above.

Risks/Impacts/Considerations

Dev Notes

The implementation details of the Convert step changes have (mostly) been thought through. Please see the Convert Step Software Requirements section in the UP Software Requirements Document.

Acceptance Criteria

• [ ] Convert Function updated per the SRD. Any changes to SRD reviewed and Approved by @arnejduranovic
• [ ] SRD updated (if needed) and Approved by @arnejduranovic

[Andrey-Glazkv]

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