Create a shadow jar with DeployDBApp as the main class
Add a simple RootResource to respond with a simple hello world string
Remove the cucumber task's dependency on assemble so we can ensure shadowJar runs checks

For some boneheaded reason the cucumber task relies on assemble which causes a
circular dependency. To make matters worse the dependency is nested inside of
`dependsOn` within an ArrayList so we must fish it out :(
Generate groovydoc for the deploydb internals for future use
Add a simple Artifact POJO to exercise some of the what Dropwizard can provide
Add a simple sanity healthcheck to make sure I can register healthchecks properly
Add the first *passing* cucumber scenario which does *actual* acceptance testing

This means we're standing up and tearing down a Jetty service inside the
process for each Scenario in cucumber for doing API documentation and testing.

Neat!
Add the cucumber-jvm generated REST API documentation to the site
Add documentation branch push hack

The only time this will be needed is if for whatever reason I've pushed the
site with locally committed changes and then rebase my local tree