Build java Event objects from received ampq messages

Created a EventJsonUtil to build useful java objects from
event json.  This should be helpful for events stored in
mongo as well, if we need to pull them out again.
Merge pull request #647 from candlepin/ckozak/read_events

Build java Event objects from received ampq messages
Move configuration code into common project.
Move logging servlet filter code to common project.
Set RequestScoped to TestScope.EAGER_SINGLETON for tests.
Move LoggingFilter into common project.
Clean up warnings in LoggingFilterTest.
Remove use of StandardCharsets as it is Java 7 and up.
Move copied dynamic filtering code into candlepin-common
Merge pull request #643 from candlepin/awood/commonize

Move common code (like the logging filter) into the "common" project.
Add docker containers for running spec and unit tests.

This will hopefully give us a solid way to run jenkins tests without a lot of
environment overhead, the container takes care of all the ruby/devel setup, and
a completely clean environment for every run. We can also now run multiple spec
tests jobs on one host system as there's no more fighting over a specific host
port.

Includes a candlepin checkout at /candlepin with all current ruby and java deps
installed to dramatically cut down on the time and bandwidth. Everything should
get updated when we run so changing deps should not be a problem, but it may be
a good idea to rebuild these from time to time. (script included see
rebuild.sh)

You can mount your host's dev checkout as a volume at /candlepin-dev when you
run if you'd like to run tests against code you're working on. I hope to add
oracle / mysql containers soon, which would mean you don't necessarily need to
set all of these up on your main system anymore.

candlepin-base container just sets up the development environment without a
database and is capable of running the unit tests successfully. It uses
supervisor to manage postgres and tomcat services as systemd is not container
friendly yet.

candlepin-postgresql layers on top of base and adds in postgresql setup,
default command runs the rspec tests.  A slightly modified version of
postgresql-setup is included as the stock one in F20 tries to read values from
systemd config which we don't have here.

Option included to open a shell once tests are complete, or you could skip
the tests to just get a shell into the dev environment you setup.
Enhance docker test script to checkout arbitrary git refs.
Symlink keystore for tomcat more reliably.

Previously we would only do this if forcecert was 1, however on a first run for
a devel system, forcecert may not necessarily be set, but certs still get
generated because they do not yet exist. The keystore would not be linked and
tomcat would not run.
How about we actually run the rspec tests?
Copy server logs out after rspec if artifacts volume exists.
Specify spec
paramaterize rebuild.sh
make -t work, more info on bad args
Don't clobber existing candlepin-base tags
Point at my custom base image