Add Parallel Cosmos Export

[mikaelweave]

Description

Adds parallel export to CosmosDB by resource type and feed range. This export does not work like SQL because CosmosDB doesn't work like SQL. It's costly to get date ranges in CosmosDB

Performance is >100K resources per second on a 100K RU CosmosDB wth 300 million documents. 20 node P2V2 App Service. Exporting history gets closer to 200K resources per second.

Related issues

Addresses AB112054.

Testing

LOTS of local testing and testing in Azure OSS. I've mainly been testing with 50 million docs in my CosmosDB.
Xoriant has also been testing with a 300 million doc db.

FHIR Team Checklist

• Update the title of the PR to be succinct and less than 65 characters
• Add a milestone to the PR for the sprint that it is merged (i.e. add S47)
• Tag the PR with the type of update: Bug, Build, Dependencies, Enhancement, New-Feature or Documentation
• Tag the PR with Open source, Azure API for FHIR (CosmosDB or common code) or Azure Healthcare APIs (SQL or common code) to specify where this change is intended to be released.
• Tag the PR with Schema Version backward compatible or Schema Version backward incompatible or Schema Version unchanged if this adds or updates Sql script which is/is not backward compatible with the code.
• CI is green before merge
• Review squash-merge requirements

Semver Change (docs)

Patch|Skip|Feature|Breaking (reason)