Adding a configuration for SMART 3rd-party IDP.

[v-isyamauchi-gh]

Description

Adding a new configuration class to accommodate a 3rd-party IDP for SMART.

Related issues

Addresses [issue #175966].

User Story 175966: Complete .well-known/smart-configuration for a 3rd-party IDP in Paas Fhir service for SMART v2.

Testing

Tested manually and by adding UTs.

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)

[mikaelweave]

@copilot Can you review this PR for spelling, and best practices?

[Copilot]

@mikaelweave I've opened a new pull request, #5314, to work on those changes. Once the pull request is ready, I'll request review from you.

[v-isyamauchi-gh]

@copilot Can you review this PR for spelling, and best practices again?

[Copilot]

@v-isyamauchi-gh I've opened a new pull request, #5317, to work on those changes. Once the pull request is ready, I'll request review from you.