Allow process selection while launching remote debugger

[andrew-woosnam]

This vsix makes its best guess as to which process on the remote belongs to the .NET app that's trying to be debugged, but it seems it doesn't always make the right choice:

Microsoft expects Visual Studio users to select the app process from a list when attaching to a remote process for debugging (source):

This VSIX should (in theory) be smart enough to know for sure what the app process name is, as long as it was deployed to CF via this extension -- it might be tough to know which running process on the remote belongs to the app in question if it was pushed by another CF user from a different environment, e.g.

Delegating the process selection to the person doing the debugging would help prevent these kinds of wrong choices