Make Liquibase migrations file an optional CLI arg

Sometimes it's desirable to maintain/package your database migrations
outside of your application JAR (e.g. when the migrations file is
massive).

Lets add an optional argument to all Liquibase Commands that permits
specifying the path to the migrations file in the local filesystem.

Omitting this option retains the default behaviour.

Note: I'm not entirely sure how best to test Command arguments, so there
are no tests. I used `dropwizard-example` to check that it roughly works
as expected, but that doesn't really qualify as testing.
Remove some unnecessary imports
Merge pull request #355 from nicktelford/feature/liquibase-configurable-file

Make Liquibase migrations file an optional CLI argument
Clean up AbstractLiquibaseCommand a little.
Leverage Servlet 3's registration API.

This allows us to drop ServletBuilder and FilterBuilder.
Pin to my new GPG keypair.
Remove JettyClientHandler.

It's a bit more than I'd like to chew right now.
Clean up DropwizardResourceConfig.
Simplify JerseyEnvironment.

This brings the API a bit more in line with Jersey 2.
Added ConnectorFactory docs.
Improve HttpsConnectorFactory.

Renamed keyStore => keyStorePath and trustStore => trustStorePath.

Added keyStoreProvider, trustStoreProvider, allowRenegotiation, and endpointIdentificationAlgorithm.
Updated the Getting Started docs.
Docs and simplification.
Fix tests.

Whoops.
Switch to enums rather than @OneOf.
Added docs for dw-spdy.

Plus came up with better names.