Rationalize hsbencher command line executable names

[rrnewton]

I propose the following scheme. We have two levels of command line interfaces.

Narrow commands:

• Each package, like hsbencher-fusion, can export one or more executables
• These have minimal dependencies and specific functionality.
• They have long, specific names, like: hsbencher-fusion-upload-criterion

Umbrella command:

• Like with git, the umbrella hsb command would be multiplexed to put all the functionality under one command
• We need to design what the namespace of sub-commands is (TBD).