[WIP] Auth service refactoring and support for "standalone" mode with multiple auth backends

This pull request includes the following changes:

* Make HTTPs optional (user can specify if HTTPs is to be used by setting `secure` option in the config file). The reason for that is that in the proxy mode when authentication happens upstream, most user will also want SSL termination to be done upstream (e.g. in Apache / Nginx / Load balancer)
* Add support for "standalone" mode. In standalone mode, st2auth service also performs the authentication using the specified backend.
* Initial support for "file" backend which reads authentication information from Apache compatible httpasswd file.
* Other improvements and polishing

TODO:

- [ ] Full documentation (about proxy and standalone mode, different backends, how to configure them, etc.)
- [ ] More backends
- [ ] Polishing

@enykeev I will ping you when documentation is there and when you can test it with the web ui. The goal should be to get it working just using the documentation - if you can't do that, this either means there is a bug or documentation is not good enough and I should fix it :)
Currently it's assumed that user manually manages the users. It's up to them to use whatever tools they like.

For a file based backend, they can use htpasswd tool from Apache utils and for MongoDB backend, yeah, they can just use MongoDB shell.

Eventually, if a need arises we could provide some tooling for managing the users - at least for the default / most used backend(s).