Make the test-webapp a separate Maven project/module

There are a handful of changes here and I apologize that the change set is kind of big.

I separated out the test web application (that registers interesting MBeans) into its own Maven build module so it can be run on its own for the demo in a couple of weeks.  The test-webapp is deployed into Tomcat launched by the fitnesse tests.

I also augmented the MBean-related fitnesse fixtures to take a JMX URL so that the fixtures can test MBeans in the (remote) Tomcat server.  This caused no end of problems, though.  It appears as though when the fitnesse tests are run in wiki mode ("wiki" goal), the Tomcat server is a separate process, but when the fitnesse tests are run as part of the regular install ("run-tests" goal), the fitnesse tests appear to run in the same process as the Tomcat server.  As a result, I had to rename all of the object names for the MBeans registered by the fitnesse tests so that the "unregister all" fixture wouldn't blow away the org.jmxdatamart MBeans registered by the test-webapp.  (This is the change to all of those content.txt files.)  

This change set also contains the removal of the "Guicy" classes from the fitnesse project.  I thought I had gotten rid of them in a previous pull request, but I think I messed something up with git.  Still learning, I guess.