Compile a ruby region observer and include it in the jar.

Jar dependes on jrubyc.  Spec depends on jar (for coming integration tests.)

The included region observer (well, coprocessor) is stolen from the spike.
Type-A.
Put hbase version numbers in coprocessor type names.

This plays more nicely with the fact that jrubyc needs everything in the root namespace.
Ditch explicit hbase versions in identifiers.

This suggests we could maintain support for many hbase versions within a single build.  This isn't very realistic when you think about automated integration testing.

Instead, we'll make careful note about which version(s) of hbase are supported by which version of the library.
Bake the hbase version number into the jar filename.

Also note the pom's (unparameterizable) version is not normative.

We have a separate library version, and our "master" version is the concatination of the two.