First production release

BalloonBot 1.0.0 release functionality includes being able to optionally configure the following via ENV variables:

# Optional configurations

FAILURE_CHANNEL_TOPIC=<Text or emoji that will appear in the topic of the deployment channel when no incident is active>

SUCCESS_CHANNEL_TOPIC=<Text or emoji that will appear in the topic of the deployment channel when there is an incident>

SLACK_HANDLE_TO_NOTIFY=<The Slack handle used to notify everyone when there is an incident. Defaults to `<!channel|channel>`. You can ping a user group/team with: <!subteam^ID|handle>, where `ID` is the team id. See https://stackoverflow.com/questions/49577969/tag-user-group-knowing-only-name-with-a-bot-on-slack>

ADDITIONAL_FAILURE_MESSAGE=<An additional message you would like to have displayed whenever anyone invokes BalloonBot "pop" or "hold">

It also includes a very bare-bones, non-styled view of all resolved incidents, ordered and filterable by the date that they were created. This can be seen at /incidents.

Note that this endpoint is guarded by HTTP Auth by default and you must set HTTP_AUTH_PASSWORD and HTTP_AUTH_USER on the platform that hosts the BalloonBot app in order to view it.