Remove clusterctl test to prepare for cmd removal
Remove fallback to npm or run

Behaviour was confusing and bug-prone, particularly when run would often
fail with a stack trace when a command was misspelled.
Remove npm and run sub-commands

npm sub-command has done nothing since we abandoned our npm fork and
private registry.

run is to be rewritten as a call to the sl-run command from
strong-supervisor.
Modify loader to help with spawned commmands

- don't require usage information in slc
- name the command after the `slc <command>`, not the function name
  (which is probably anonymous, "")
- don't steal the -h or --help option from anywhere in the argument
  list, in `slc run script.js --help`, the `--help` isn't an option to
  `slc`, or to `slc run`, but to `script.js`, optimist gets this really
  wrong
Implement `slc run` as strong-supervisor/sl-run

Run sub-command now simply calls the sl-run command from
strong-supervisor.
Implement `slc debug` as node-inspector/node-debug

Run sub-command now simply calls the node-debug command from
strong-supervisor.
Implement `slc clusterctl` with clusterctl

Run sub-command now simply calls the sl-clusterctl command from
strong-cluster-control.