Remove Storage Account Keys and SQL Passwords from Tests

[mikaelweave]

Description

Updates SQL and Storage tests to use service connection to Azure for auth vs key/password methods. This change requires:

• Changing auth to use AzurePipelinesCredential
• Adding a custom SQL auth provider since SQL doesn't support this credential scenario.
• Deploying a new SQL Server for integration tests. We can't use the same server because:
  • We can't attach the managed identity with access to the main SQL Server to the pipeline execution environment.
  • You can only have one SQL admin
  • Granting an AAD principal access to the database w/ automation requires that the managed identity attached to the SQL Server has Directory.Read permissions.
• Disabled 3 blocking tests and created work item.

Related issues

AB#122686

Testing

• PR pipeline is passing

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)