Retaining status of Unsupported search parameters

[rajithaalurims]

Description

Each FHIR version has a set of unsupported search parameters. Recent code changes introduced a regression and marked those search parameters as Enabled. As a result, when customers search with those parameters, we return 500 instead of a 200 response with a warning message.

This PR updates the behavior so the status of Unsupported search parameters stays intact when a new FHIR service is created

Related issues

Addresses [issue #197702].

Testing

Integration and E2E tests added.
Created new FHIR service and confirmed status of Unsupported search parameters is as expected

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)

[rajithaalurims]

/pr

[rajithaalurims]

/azp run

[azure-pipelines]

Azure Pipelines:
Successfully started running 1 pipeline(s).