Refactor core into plugins with command and subcommand scripts

This change makes the mapping of plugins to commands in Dokku significantly
more consistent, giving each existing Dokku command its own plugin, and each
plugin a dedicated location for a provided command and/or subcommands.

Beyond the navigational advantages, this allows individual commands /
components of Dokku to be disabled or overridden at the plugin level, without
having to muck around patching scripts that provide unrelated commands.

"command" scripts, like a hook, are executed when the name of a plugin is
called: for instance, "dokku build" calls the "build" plugin's "command"
script (plugins/build/command).

"subcommand" scripts are called for subcommands of plugins, as namespaced with
a colon: for example, "dokku backup:export" calls the "export" subcommand
script of the "backup" plugin (plugins/backup/subcommands/export).

Plugins that do not use their name for commands/subcommands (such as the git
plugin, or plugins that wrap other commands) can continue to use the "commands"
hook, which remains fully supported and backward-compatible.

Each plugin / command gets a README describing its purpose and implementation.

Additionally, the "help" text describing its commands' usage is moved out to a
separate "help.txt" file, which is then read and (potentially) columnized when
running the "help" command.

This commit also removes the "warning" in the plugins directory - Dokku's
stability, hooks and all, is covered by the main Dokku README.

This commit also removes the nginx-vhosts plugin's functionally-empty
"commands" hook script, for clarity and cleanliness.