Bump actions/setup-dotnet from 2 to 3

[dependabot[bot]]

Bumps actions/setup-dotnet from 2 to 3.

Release notes

Sourced from actions/setup-dotnet's releases.

v3.0.0

This major release includes the following changes:

• #219 New input dotnet-quality was added in #315:

    - uses: actions/setup-dotnet@v3
      with:
        dotnet-version: '6.0.x'
        dotnet-quality: 'preview'
    - run: dotnet build <my project>

More in detail here.

• #241 The output variable dotnet-version which contains the installed by the action SDK version was added in #324:

    - uses: actions/setup-dotnet@v3
      id: cp310
      with:
        dotnet-version: '3.1.422'
    - run: echo '${{ steps.cp310.outputs.dotnet-version }}' # outputs 3.1.422

More in detail here.

• The dotnet-version syntax was updated and now it allows to specify the prerelease version without using include-prerelease input. The include-prerelease input was cut out:

    - uses: actions/setup-dotnet@v3
      with:
        dotnet-version: '5.0.0-preview.6'

More in detail here.

• #251 The problem with out of support .NET version warnings was solved in #315.

Breaking changes:

• Installation paths for Windows and Ubuntu images were changed to match the location of pre-installed SDKs. In more detail, read here.

Add support for Windows-arm

In scope of this release we add support for Windows-arm. Besides, we change getInput to getBooleanInput for include-prerelease.

Package updates, support for global json file in a subdirectory, installer scripts updates

This release includes the following PRs:

• Adding support for the global-json-file input: #276 Example of usage:

  - uses: actions/setup-dotnet@v2
    with:
      global-json-file: csharp/global.json
  - run: dotnet build <my project>
    working-directory: csharp
  

... (truncated)

Commits

• c7e7147 Add ability to write resolved version of SDK into the output variable (#324)
• 0705ef0 Implement proposal stated in ADR for setup-dotnet v3 and functionality from f...
• See full diff in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)