feat: Execute a script command via CLI like `hubot -e some command` (#…

…1734)

* testing

* feat: Execute commands in scripts on the CLI via hubot -e <some command>

fix: #1732 Passing -d should disable the http service" (#1733)

* fix: #1732 Passing -d should disable the http service"

* Fix standards issues

fix: having to hit the up arrow key so many times to get to the previ…

…ous command

fix: standard

feat: Shell adapter no longer requires starting the message with the …

…robot name.

BREAKING_CHANGE: When using the Shell adapter, it is no longer required to start with the robot name. When before you had to type `Hubot help`, now you can just type `help` and the help scripts will respond.

fix(Shell): Sometimes up-arrow wasn't showing history

fix(Robot): warning function doesn't exist message when the regex sta…

…rts with an anchor

fix(Shell): History wasn't working when hitting the up and down arrows

fix: Scripts making pipelined requests were not waited on to finish b…

…efore loading the next script.

I observed a bug when using Azure app-configuration to get app configuration values from Azure's App Configuration service to create a robot.config object for other scripts to get values from. appConfigClient.getConfigurationSetting pipelines requests and the other scripts (which depended on this one to complete) were being loaded before getConfigurationSetting returned, resulting in a race condition where other scripts failed to load because they depended on robot.config to have the values from App Configuration.

fix: Scripts not loaded in the order they exist in the file system