Default Selected Projects doesn't make sense with Selected Package in Solution PM UI

[nkolev92]

Issue motivated by the following feedback issue:
https://developercommunity.visualstudio.com/content/problem/84482/nuget-solution-package-manager-user-experience-is.html

It's related to the "intuitiveness" of the Update tab in the UI.
Here's the comment from the user.

See the attached (capture-1.png). The Update tab is selected. On the left-side System.ValueTuple is selected. On the right the Microsoft.Alm.EndTask and Microsoft.Alm.GitProcessManagement projects are selected because of a previous operation. However, neither of them have the selected nupkg installed, and neither can be updated. To the far right of the project name is the version column, but it's significance is diminished when compared to the checkbox column.

The real confusion comes in here: I have chosen to update my installed nupkgs, yet the interface insists on selecting project which cannot be upgraded (because they've not even got the package). When in a hurry, I could quickly the Install button thinking that I'm updating the already installed nupkgs, when in fact I'd be incorrectly installing an updated nupkg into an unwanted project.

Now, let's get really crazy. See the attached (capture-2.png). The Update tab is still selected. On the left-side either Microsoft.Net.Compilers or System.ValueTuple is selected, and there's no immediate way to tell if one or both are actually selected (this capture required me to launch Snipping Tool then go through the motions of taking the capture - yet the blue highlighted area remained to be captured, how thoughtful -- and confusing!). In this instance Microsoft.Alm.Echo and Microsoft.Alm.GitProcessManager have checked boxes; only Microsoft.Alm.Echo have a version number tucked away on the far right-side. Now both Install and Uninstall are enabled - honestly, I've been too frightened to have tried clicking either button so I have no idea what would happen - regardless, this seems like a completely invalid state.

So the net-net here is: the UX contradicts itself. The Update Tab can install and uninstall packages. The selection of projects is sticky between navigating to a new package, despite the selections becoming potentially invalid. It is possible to faux-multi-select packages. The indication of a project-package relationship is least obvious element in the entire UX despite potentially being the most important.
Thanks for listening, here's hoping the UX improves in Dev16 :-)

[rrelyea]

@PatoBeltran - put into your backlog. Please help prioritize this with your other issues.

[mishra14]

I tried this scenario and it does seem like we do not refresh the right pane when the package in the left pane is changed.