Log helpful messages when keystone connection is misconfigured

Add new useHttps configuration to control whether to use https
when talking to keystone. Old way was based on port which doesn't
seem to give enough control

Return 500 to client instead of 401 if the keystone authentication
is misconfigured.

Add more logging to help user determine what is wrong if the keystone
authentication is misconfigured

Check keystone authentication configuration on startup and exit if it
is set properly

Remove serviceIds and endpointIds from configuration because those
aren't used the keystone v3 and that is all the API will support

Change-Id: I988878f69e06f47bb87f6f2663e498e019810c4c
Add alarm delete resource

Change-Id: Ie6a68f48cbbb8626dbff2381f741b7e5fb4d6fe7
Merge "Add alarm delete resource"
Merge commit '000056f1748507732ae996eb994177201f6bbc5b'