EOL .NET 5.0 install may fail with setup-dotnet v5 #4953
Description
See comment from Cursor bugbot below. We may need to remove the use of .NET 5 in our CI builds.
The implication is that we wouldn't catch warnings with our analysers when SDK users are using Sentry in Visual Studio 2019.
Both Visual Studio 20190 and .NET 5 are ancient, so I think that's OK.
Originally posted by @cursor[bot] in #4948 (comment)
EOL .NET 5.0 install may fail with setup-dotnet v5
High Severity
The actions/setup-dotnet was bumped from v4.3.1 to v5.1.0, but v5.0.0 explicitly lists "Remove Support for older .NET Versions and Update installers scripts" as a change. The "Install .NET 5.0 SDK" step still attempts to install dotnet-version: 5.0.x using the v5.1.0 action, but .NET 5.0 is end-of-life and the updated installer scripts in v5 may no longer support it. This could break CI for all workflows that use this shared environment action.
