Release vNext

[blairconrad]

• Address all coding and style violations detected during a Release build (send a regular pull request which must be merged before continuing)
• ensure completeness of draft release notes, including non-owner contributors, if any (move release notes forward from any pre-releases to the current release)
• ensure that the analyzer still works with the versions of Visual Studio listed in the docs
  @blairconrad checked on VS2022 as indicated in the comments below
• run tools\prepare_release.cmd next x.y.z vNext to:
  • change "vNext" names to appropriate x.y.z version for the next GitHub Release, milestone, and release checklist (this issue)
  • create a new draft GitHub Release, milestone, and release checklist
• tag master with the new version number and push to upstream. This will cause the build server to
  • push the nupkgs to nuget.org,
  • attach all nupkgs from the tagged build to the GitHub Release,
  • add a comment to each issue and pull request in the release, saying it was published in this release
• wait for NuGet package validation
• de-list pre-release NuGet packages if present
• publish the GitHub release
• tweet, mentioning contributors, and post link as comment here for easy retweeting ;-)
• post tweet in Gitter
• add a note in each issue that has a significant contribution from a community member, thanking the contributor
• close this issue
• if this is not a pre-release, close the milestone for this release