Switch verb and noun for package/reference add/remove/list Fixes #9650

[Forgind]

Fixes #9650

Switches the ordering of commands from dotnet verb noun to dotnet noun verb, as it is sometimes unclear what 'add' adds, for instance, and this is how many users of other CLIs think.

In this version, dotnet verb noun (DVN) is still supported in that it works when used, but dotnet noun verb (DNV) is the priority. DVN is now hidden and doesn't appear in the help text, whereas DNV is visible and does appear in the help text.

Incomplete:
We need to change how we accept arguments. This is still a point of discussion, so we need to build consensus on the right order before proceeding. (Possibilities include dotnet package <package> add <project>, dotnet package add <package> --project <project>, etc.)
We should consider adding a message when using DVN directing users to DNV

[JonDouglas]

[aortiz-msft]

@OliaG , would you please review the UX changes proposed?

[Forgind]

Things look like they're starting to work:

[MiYanni]

Looks good! A majority of the changes were moved files so it wasn't so large as it seemed. Only question I had was how the docs should be updated. But we can discuss that offline with @baronfel

[MiYanni]

This shows my unfamiliarity with this but why does both ForwardedOption's constructor and ForwardAs have the same string for bool options?

[Forgind]

Er...great question. I didn't even notice; as you pointed out, a lot of these changes were just moving things from one file to another, and this is an example. @baronfel?

[Forgind]

baronfel told me that ForwardedOption is an option with a null forwarding function—that is, it doesn't actually specify how it should be forwarded, just makes that possible if you also specify ForwardAs and how to forward it.

[baronfel]

We'll need to doc this in the 10.0 preview 2 release notes and in the 9.0.300 changelogs (for future-Chet's reference).