Deprecate NuGet.exe list in favor of NuGet.exe search

[dominoFire]

Following the deprecation effort in commands to avoid ambiguity, the nuget.exe list command will be renamed to nuget.exe search.

Why we are renaming?

1. The dotnet.exe list command lists package or project references in projects or solutions, which is different from listing packages from a feed in the actual nuget.exe list behavior. To avoid confusion between those commands, we want to set a more adequate verb for describing the actual nuget.exe list behavior.
2. We want to implement new search filters.

How this will be?

First we'll both commands available in nuget.exe; both of them will have the same functionality, except for nuget.exe list, that will display a deprecation warning message each time the command is invoked.

In the upcoming releases, we will remove the nuget.exe list command.

The issue tracking all the deprecated commands is : #7753

[JonDouglas]

I'm not a fan of deprecating a command purely because its name. This tool has used a specific command for many years before a new one is introduced.

Let us use simple aliases instead.