Fix instance availability errors following schema upgrade

[rbans96]

Description

We have seen that after schema upgrade, as soon as the current schema version changes for an instance, the instance since not initialized upto the current schema version returns 503 and thus it impacts the customer experience.
This PR ensures that instance should be initialized upto the min supported schema version and if there is a schema upgrade, service should continue to respond while initializing the instance in parallel.

Related issues

Addresses [issue #].
https://microsofthealth.visualstudio.com/Health/_workitems/edit/139949

Testing

Describe how this change was tested.

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)