Create REST API for administering the bot

[gazbert]

Create a REST API for managing the bot.

The initial release will support:

• Configuring the bot.
• Restarting the bot.
• Fetching the bot logs.

It will be secured using TLS and JWT.

It will be documented using Swagger.

It will be consumed by BX-bot UI (#101) and 3rd party apps.

Later releases will support:

• Fetching metrics for stuff like CPU, memory, disk, and JVM stats.

[gazbert]

Still to do:

• Endpoint to to start|stop|status the bot
• OAuth2 security: Keystores, credentials, etc...
• Audit/access logging

[gazbert]

Still ToDo:

1. New Runtime endpoint to: start|stop|status the bot, fetch/tail/download bot log, fetch bot resource usage, e.g. memory, cpu, disk.
2. Make a decision on whether REST API should expose sensitive API keys/secrets for Exchange config... Same too for the Email Alerts config SMTP account password. Currently, it does not. These are things that users would not change very often - I'm thinking these config items should never leave the bot node? Nervous a bug in my (JWT/HTTPS) implementation could leak someone's API creds... Or someone spins up the bot/UI without configuring TLS... Or am I just being paranoid? ;-)

[gazbert]

Outstanding Work (Almost done!)

• [x] Boost test coverage.
• [x] Swagger mandatory fields + head/tail log query params.
• [x] Update Gradle build for JBehave, Swagger, code coverage.
• [x] Upgrade all dependencies + new bot release version.
• [x] Fix broken REST API tests in Gradle build.
• [x] TLS configuration - test + docs.
• [x] Fix Sonar issues.

[gazbert]

Sonar issues need fixing then ready to go... finally!

[gazbert]

Released.