Recommend using NuGet v3 repositories for Nexus and Artifactory

## What New Or Updated Would You Like To See?

After investigating an [issue raised regarding NuGet v2 repository types in Sonatype Nexus and JFrog Artifactory](https://github.com/chocolatey/choco/issues/3270), we found there was a bug in the API responses. This bug is not present in NuGet v3 repositories. [I updated the issue with this information](https://github.com/chocolatey/choco/issues/3270#issuecomment-1816777233).

Oridnarily we'd suggest raising issues with the repository managers directly. However, with NuGet v2 repository support being reduced / deprecated in [Nexus](https://help.sonatype.com/repomanager3/nexus-repository-administration/formats/nuget-repositories) and [Artifactory](https://jfrog.com/help/r/jfrog-release-information/artifactory-deprecations), there's unlikely to be much traction in those being fixed. Other repository managers are likely to follow.

To ensure customers and community have the maximum lifespan from their repositories, we should ensure NuGet v3 repositories are recommended in documentation and other communications.

When troubleshooting a NuGet v2 repository issue we should ensure it can be reproduced in a NuGet v3 repository.

The list below is the work that needs to be done but is not an exhaustitive list. As we find more we will update it:

* [ ] Ensure the Quick Start Environment deploys a NuGet v3 repository.
* [ ] Ensure Chocolatey For Business Azure Environment deploys a NuGet v3 repository.
* [ ] Ensure Chocolatey For Business Ansible Environment deploys a NuGet v3 repository.
* [ ] Ensure any scripts in our documentation setup a NuGet v3 repository.
* [ ] Ensure that any recommendations we make about repository types in our documentation is for a NuGet v3 repository.
* [ ] Ensure when we talk about caching repositories that we make it clear, and reference the souce, that tere may be issues with a NuGet v2 caching repository.
* [ ] Where we talk about internalization, we should ensure it makes it clear that this issue does not affect internalized packages.
* [ ] Produce a migration plan, from NuGet v2 to NuGet v3 repository types, for customers and community.
* [ ] Write a blog post announcing this change to ensure as many customers and community are aware.