Adds .net 9 support

[brendankowitz]

Description

Adds .NET9 build target and changes Docker images to use .NET9 on AzureLinux.

Framework and SDK Updates:

• Updated the target frameworks in Directory.Build.props to include net9.0 along with net8.0 and net6.0.
• Modified global.json to use SDK version 9.0.102 for the project.
• Updated the Dockerfile to use .NET SDK 9.0.102-azurelinux3.0 and runtime 9.0.1-azurelinux3.0. [1] [2]

Package Version Updates:

• Updated HealthcareSharedPackageVersion to 8.0.30 and added conditional package versioning based on the target framework in Directory.Packages.props. [1] [2]
• Updated various package versions, including Azure.Identity, Microsoft.SqlServer.SqlManagementObjects, and System.Data.SqlClient. [1] [2] [3]

Build Pipeline Modifications:

• Updated the default build framework to net9.0 in build-variables.yml and added a new job for Windows_dotnet9 in ci-pipeline.yml and pr-pipeline.yml. [1] [2] [3]
• Added a new job for Windows_dotnet8 in ci-pipeline.yml and pr-pipeline.yml to maintain compatibility with .NET 8.0. [1] [2]

Code Analysis and Suppression Rules:

• Added suppression rules for CA1852 in the CustomAnalysisRules.ruleset file.
• Applied code analysis suppression attributes in SmartLauncher classes to address maintainability and performance warnings. [1] [2]

Miscellaneous Updates:

• Updated the .NET 6 SDK version in build/dotnet6-compat/global.json and added global.json for .NET 8 compatibility. [1] [2]
• Changed the visibility of SmartLauncherConfig and Program classes to internal in SmartLauncher project. [1] [2]

These changes collectively enhance the project's compatibility with newer .NET versions, streamline package management, and improve the build and deployment processes.

Related issues

Addresses AB#136374

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)

Feature (new framework target)

[feordin]

Do we want to allow any rollforward to minor versions? Or keep it as is to a specific version?

[brendankowitz]

Mikael had a different PR trying to address this - #4687. This PR is just adding the new target