Untangle the slc run/slc npm/slc xxx mess

https://strongloop.atlassian.net/browse/SLN-608
https://strongloop.atlassian.net/browse/SLN-649

/to @raymondfeng 
/cc @altsang @chandadharap @Schoonology 

We should delete the npm and run sub-commands, they don't do anything except create problems and maintenance burdens (untested, weird behaviours, that don't appear to be valuable or used by anybody). Also, they are architecturally inconsistent with the agreed direction: CLIs per strongloop suite component.

```
echo 'console.log("hi")' > install.js
node install // hi
slc install // does npm install... ok, that's a builtin command, fine
slc run install // does npm install.... ?
slc insTall // does slc run install, which has IDENTICAL output to node xxx, a long stack trace, as it is documented to
```

slc install has some value, we want to add features to the install, for better platform support, in the future, and don't want to strip it out of all our docs. https://strongloop.atlassian.net/browse/SLN-610

slc run is a problematic version of 'node'
slc npm is a problematic version of 'npm'

We should delete them.