Set .NET used by our tools to net6.0 + minor updates to .sln files

[konrad-jamrozik]

This PR addresses issues #4888, #4934 and #4935 for the following tools and other projects, by migrating their target frameworks to net6.0, and ensuring that their ci.yml sets DotNetCoreVersion: 6.0.403:

• version-guard;
• CreateRuleFabricBot and its tests;
• code-owners-parser and its tests. This required disabling execution of get-codeowners.ps1 script as part of the test suite. Follow-up work to re-enable it: Re-enable code-owners-parser get-codeowners.ps1 test script after migration to net6.0 is done #4938;
  • Update 12/28/2022: I missed some things to update here; PR updating the leftovers:
  • Update <TargetFramework>netstandard2.0 to net6.0 in Azure.ClientSdk.Analyzers and CodeOwnersParser #5029
• notification-configuration;
• identity-resolution;
• generator (i.e. Stress.Generator) and its tests;
• Azure.ClientSdk.Analyzers and its tests;
• SwaggerApiParser. This only required setting ci.yml to point to .NET 6, as it was already targeting net6.0;
• snippet-generator and its tests;
• tools\agent-time-extractor\AgentTimeExtractor\AgentTimeExtractor.csproj;
• src\dotnet\APIView\TestLibrary\TestLibrary.csproj, which was using netcoreapp2.1 which is out of support since August 2021, but the APIView pipeline and the pipeline seems to be failing due to unrelated reasons, so usage of netcoreapp2.1 seems to be non-blocking. Nevertheless, I updated it to net6.0 anyway;
• Azure.Sdk.Tools.HttpFaultInjector;
• Azure.Sdk.Tools.HttpFaultInjector.StorageBlobsSample;
• Azure.Sdk.Tools.HttpFaultInjector.HttpClientSample;
• Sample projects of TestProxy, but not the TestProxy itself, as it was already on net6.0, albeit it also targets net5.0, which I left unchanged;
• PixelServer, which required adding an import to Program.cs. Note I couldn't find a corresponding ci.yml or pipeline for it.

Tools not updated to net6.0 in this PR

<TargetFramework> occurrences not migrated as part of this PR, and why:

• Any tools targetting netstandard as it is compatible with .NET 6.0;
• tools\pipeline-generator\Azure.Sdk.Tools.PipelineGenerator\Azure.Sdk.Tools.PipelineGenerator.csproj, because it is done in PR Update PipelineGenerator target framework from netcoreapp3.1 to net6.0 #4915
• tools\check-enforcer\Azure.Sdk.Tools.CheckEnforcer\Azure.Sdk.Tools.CheckEnforcer.csproj, as it uses archetype-sdk-tool-azure-function.yml archetype, which doesn't support the DotNetCoreVersion override. CheckEnforcer currently targets netcoreapp3.1;
• tools\github-issues\Azure.Sdk.Tools.GitHubIssues\Azure.Sdk.Tools.GitHubIssues.csproj, for the same reason as check-enforcer. GitHubIssues currently targets netcoreapp3.1.
• tools\webhook-router\Azure.Sdk.Tools.WebhookRouter\Azure.Sdk.Tools.WebhookRouter.csproj, for the same reasons as check-enforcer. WebhookRouter currently target netcoreapp3.1.

Additional remarks

For a list of all PRs doing migration to net6.0, see this comment:

• The template for prepare-pipelines is broken by the move to ubuntu-22.04 #4888 (comment)

As a secondary mini-refactoring, this PR also adds ci.yml files to corresponding .sln files and updates the .sln files Visual Studio version used to VS 2022.

[mikeharder]

Approving changes under tools/http-fault-injector

[benbp]

+1 thank you for doing this! For check-enforcer and possibly webhook router, we can start to delete those projects entirely, I think. @hallipr just to double check, nothing of yours relies on the webhook-router eventhubs, right?

[konrad-jamrozik]

@benbp

For check-enforcer and possibly webhook router, we can start to delete those projects entirely, I think.

If so, I will make a separate PR to delete these projects.

@weshaggard I am merging, assuming Ben's approval is enough. Let me know in case that's incorrect assumption xD

[weshaggard]

LGTM

[konrad-jamrozik]

@benbp @hallipr created PRs to delete the two obsolete projects:

• Delete obsolete CheckEnforcer tool #4963
• Delete obsolete WebhookRouter tool #4966