(SERVER-112) improve bootstrap test

(SERVER-112) rename dev sample config file
    
We were not being consistent in our naming of our various sample
config files.  This commit simply renames the main puppet-server.conf
sample file to be more consistent with the other sample files.

(SERVER-112) rename testutils namespaces to be more specific
    
This commit simply renames the `jruby/testutils` and `ca/testutils`
namespaces to `jruby-testutils` and `ca-testutils`.  In a subsequent
commit I will be introducing another new testutils namespace, and
was concerned that we were going to start piling up too many files
named `testutils.clj`.

(SERVER-112) Introduce bootstrap testutils, improve bootstrap test
    
Prior to this commit, the bootstrap test wasn't actually doing
much work.  It would create a trapperkeeper app to make sure that
there were no failures in just loading the service *namespaces*,
but it did not call any of the lifecycle functions of any of the
services, so would not actually do much in terms of validating
that the app could be run.
    
This commit improves the test to make it actually do a full startup
of the app based on the sample config files.
    
It also introduces a bootstrap_testutils namespace, which contains
some test utility code relating to booting up a puppet server
instance during testing.  This will be useful for some forthcoming
tests that I am writing related to testing puppet's directory
environments.
Yeah, not sure.  The first one was kind of intended to validate that we're actually able to evaluate code inside of the macro (while the server is running), and the second one was just to make sure that we exited from the macro successfully.  I suppose they're both debatable, but probably harmless.  Happy to tweak if anyone has suggestions that they feel will improve it.