Add graceful shutdown and a shutdown hook in Application.

[Ewen Cheslack-Postava (ewencp)]

The graceful shutdown period, during which new requests are rejected but
outstanding requests are allowed to finish, is configurable. A shutdown hook in
Application also allows additional resources not associated with any single
request to be cleaned up. In order to ensure the process does not exit before
the hook runs, lifecycle methods are added to Application that wrap and augment
the ones in Jetty's Server class.

[Ewen Cheslack-Postava (ewencp)]

Jun Rao (@junrao) probably makes sense for you to review this since you'll want to make sure it suits your needs for schema-registry. I have a version of rest-utils that cleans up some shared state on shutdown using this, so I think this should be good enough. See the example app for the modifications to main() that you need to make since Application now wraps the Jetty Server completely for start/stop.

[Ewen Cheslack-Postava (ewencp)]

Jun Rao (@junrao) Do you want to look over this to make sure it'll work for schema-registry before I merge? It has some other incidental changes that I need to address another issue, so I'd like to get it committed.

[Jun Rao (junrao)]

Should we make this an abstract method to force the subclasses to define onShutdown()? Most apps probably have some resources that they need to clean up on shutdown.

Other than that, the patch looks good.

[Ewen Cheslack-Postava (ewencp)]

I considered that since I agree most apps probably have some resources that should get cleaned up gracefully, but doing so doesn't scale down to tests and simple apps like the example. You end up having to implement methods just to leave them empty. I'm going to leave it as is for now but we can always revisit.