Bump Microsoft.CodeDom.Providers.DotNetCompilerPlatform from 3.11.0 to 4.1.0

[dependabot]

Bumps Microsoft.CodeDom.Providers.DotNetCompilerPlatform from 3.11.0 to 4.1.0.

Release notes

Sourced from Microsoft.CodeDom.Providers.DotNetCompilerPlatform's releases.

v4.1.0 release

• Refreshed current compilers: In keeping with the new versioning scheme for this project, the version has been revved to 4.1 to match the version of the compilers included.

• No more old compilers: Stop carrying old versions of compilers. If you upgrade to get new compilers, you get new compilers. The old compilers that might carry references to binaries that get flagged in security scans even though the binaries don't get copied to the ouput directory... they just won't be included in the package anymore.

• .Net >= 4.7.2 Required: As a result of not keeping older compilers packaged in this project, we can no longer support versions before 4.7.2 because compiler versions 3.0 and newer only support 4.7.2+.

• Move to msbuild targets - away from install.ps1: Nuget has moved on from install.ps1. We had one foot in the msbuild camp before, and one foot still in the install.ps1 camp. The 4.X releases jump fully into the msbuild ecosystem with both feet.

v3.11.0 release

Refresh compilers to 3.11... the most recent and likely last of the 3.X major releases.

• Refreshed compilers: In keeping with the new versioning scheme for this project, the version has been revved to 3.11 to match the version of the compilers included.

• Only support .Net >= 4.6.2: Older versions of .Net are out of support, so this update also removes support for them and no longer carries the oldest version of the compiler tools that was used in previous versions.

• Non-web projects: The appSetting aspnet:RoslynCompilerLocation can still be used to point at a specific download of the Roslyn compiler tools, but this package is hopefully a little more forgiving when searching for a default location and should accomodate both web projects as well as non-web projects without requiring this setting.

Commits

• 919235a V4 fork (#148)
• 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)