introduce a DefaultManager class that we'll use with context.setManager

as a StandardManager replacement - due (session) secure random init
use a custom context manager to have "truly" lazy (java) sessions (#123)

this avoid secure random generation for session ids during server start
allows for (package level) sharing of some of DefaultFormatter helpers
re-invent the MessageFormatter in Java
use the LoggingHelpers with DefaultFormatter
Jerry - Tomcat's little companion

this Tomcat replacement "embed" entry point we're using has been introduced due latest changes since 7.0.41 (7.0.47) where if a context.xml is missing we end up with exceptions ...
update TC to 7.0.47 as well as build trinidad-rb.jar - trinidad_jars 1.3.0

... also we're now exposing Trinidad::Tomcat as "our" Tomcat instance
start using Trinidad::Tomcat
we're getting more "strict" about jruby-rack and trinidad_jars gem versions
do not prefix everything with the Trinidad constant
use absolute path and log info when generating keystore
only generate 'dummy' SSL keystore if not done already (fixes #117)
make sure we keep localhost for tomcat.server's address if not spoecified
handle underscore ssl options + allow to specify connector's protocol
prepare for better ssl/ajp connector defaults - support https: alias for ssl:
better handling of port/address for connectors when only one configured
e.g. in case users want https:// but not http://
default :port for SSL is now (a more Ruby-sh) 3443
log info when default (non-configured) keystore is being used
improve port defaults for connectors - http (still) 3000 https 3443