Expose Cosmos Direct Mode Connection Config

[mikaelweave]

Description

Exposes CosmosSDK direct connection configuration values for CosmosDB backed FHIR Servers.

Note - a value of null is what we are passing to the configuration via the builder for all of these configuration values today (except for enableTcpConnectionEndpointRediscovery which we explicitly set to true).
https://github.com/Azure/azure-cosmos-dotnet-v3/blob/master/Microsoft.Azure.Cosmos/src/Fluent/CosmosClientBuilder.cs#L445

Related issues

AB#140094

Testing

Run code to confirm configuration flows from env variables to client creation.

default

w/ overrides

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.
• When changing or adding behavior, if your code modifies the system design or changes design assumptions, please create and include an ADR.
• CI is green before merge
• Review squash-merge requirements

Semver Change (docs)

Patch|Skip|Feature|Breaking (reason)