next trinidad shall depend on latest jars and jruby-rack
(initial) fail-safe zero-downtime support for rolling reload
when a new version if the app fails to boot the old one is kept
make sure starting new context works during rolling reloads

just in-case we make sure StandardHost has it's startChildren flag disabled when creating the new context

also due ContextAccessController magic make sure name is not changed and is kept during lifecycle even if (slightly) different from WebApp's context_name