Support creation of custom API endpoints to execute commands

[clockworksoul]

Cog had a really nifty feature that allowed privileged users to create custom API endpoints -- additions to the Cog REST API -- that could be used to trigger commands (Cog called them triggers, but they’re just custom API endpoints). This allowed Cog to be integrated into CI pipelines or other workflows without having to send text to Slack to trigger commands.

• Important question: how would security for these endpoints work? (At the very least they'll require an API key)
• Cog triggers were defined on the command line, with the command to execute. We’d require them to be defined via config (including the command to be triggered, and where to direct the output).
  • Should we allow the base config to define a default output chat+channel?
• The executed command would have its own environment variables