meerkat.RegionObserver is a pure-java region observer.

This will be the actual entry point listed in coprocessor specs.  It will use MeerkatEnvironment (actually renamed to meerkat.Environment) to bootstrap jruby and set up the delegation to the actual ruby impl.
Prove we can load a coprocessor from fixture.

I apparently need to change gears and deal with cache-busting hbase's class loader logic.
Bust hbase's coprocessor classpath cache with tempfile symlinks.
Wrap hbase context bootstrap code in a global before block.

Ideally we'd run this code only if the shared context actually gets used, but only *once*, evar.  A before block in the shared context would be run once per suite.
Rename tasks/example_app.rb -> tasks/prep_example_app.rb
Make a failing test.
Start and stop an environment in the region observer.

Try to make environmental state changes atomic, since we've demonstrated that coprocessors must be thread safe.  Thus start/stop are synchronized and the environment member itself is volatile.  Further, don't setup or teardown the published member; swap with a null local and do life cycle stuff privately.