Adding a container configuration parsing logic stuff

First parts to build the container configuration information to get the
necessary SSL stuff in there
Working on the new ConfigurationWatcher, to watch multiple files...

Slightly more complicated :(
Updating tests to verify functionality for both files.
Ignoring entire test :(

Not because I want to, but because testing the system level APIs is not
working very well. I should probably have this built differently...
Refactoring on the node store

Adding better node starting behavor for those actors, as well, modifying
the actors behavior to take a ConfigurationUpdated message, and adding
the container configuration path
Refactored node list 1 tests
Removed this test, as it doesn't do anything useful at this point
Updated test to deal with a different starting point, just to be sure
Fixed up the Launcher

Now everyting runs on initialization of the actor. The nodeStore is
configured with a supervision strategy of PANIC. Any exceptions that
make it out of the actor will bring the entire system crashing down.
Created some properties, and some logging properties

This way I can see wtf is going on much easier
Wanted to get the full command debug logged, so yay
Added the logic for handling the container config
Refactored this a BUNCH to handle two files, instead of just one
Adding the test cases pending for a container config and insecure
Failing test, and notes about how to do things!
I don't want to have to manually configure my log4j while testing

So this!
Created test for jetty configuration generator.

Created sample xml files to compare with generated XML.

Read lots of XML config files...
Adding reference location
Handle --insecure !
Adding Jetty config generation logics