First stab at more human configuration errors

    * `ConfigurationException` has been made abstract and broken out in
    to `ConfigurationParsingException` and
    `ConfigurationValidationException` to properly encapsulate the
    different kinds of errors.
    * `ConfigurationFactory` catches a variety of common Jackson and
    SnakeYAML `Exception` and attempts to turn them in to sane
    `ConfigurationParsingException`s.
    * When provided with _suggestions_, `ConfigurationParsingException`
    will provide the user with the top-5, fuzzy matched against their
    input by Levenshtein distance.
Suppress stack-traces for ConfigurationExceptions.

Stack-traces are for unexpected program errors. ConfigurationExceptions
are an expected consequence of an invalid runtime configuration.
Therefore, the stack-trace adds no information of value.

Lets suppress it so it's less likely to scare people.
Remove docs for non-existent constructor parameter
Merge pull request #368 from nicktelford/feature/human-config-errors

More human configuration errors
update to liquibase 3.0.4
Merge pull request #392 from kutzi/liquibase-3.0.4

update to liquibase 3.0.4
Upgrade to Metrics 3.0.1.
Upgrade H2.
Upgrade Objenesis.
Upgrade to Jetty 9.0.5.
Upgrade to Jackson 2.2.3.
Upgrade to httpclient 4.3.
Upgrade to Hibernate 4.2.5.
Upgrade to Joda Time 2.3.
Upgrade to Guava 15.0.
Update relnotes.
Move from com.codahale to io.dropwizard.

I registered the dropwizard.io domain the other day, and it should be
the new home for Dropwizard. This should make it easier for me to build
out better governance around the Dropwizard project.
Trim some crap.
Fix GitHub links.
Add option to include stack traces in syslog

Syslog doesn't work well with stack trace data. The Logback
`SyslogAppender` provides an option to exclude this data, logging only
the name of the Throwable and its message.

We should provide this option to users.