Add dependency management for private RV-Monitor

@grosu @dwightguth @seriousamlqz @kheradmand @xiaohe27 @owolabileg 

Please see the new README for instructions on the process for non-RV developers.  For RV developers who have access to our private Maven repositories, the additional step is optional and nothing will change from the current process.

This build has NOT been tested on Jenkins and using the automatic dependency resolution mechanism.  It is likely not to work because of the version range changes I have made, so please wait for my all clear before merging.

After this is merged the next step will be to move RV-Monitor to an internal private repository and remove it from our public repository management.  At that point there will be no unlicensed distributions of the RV-Monitor jar around.
I find it a bit confusing, because people may think they should have access to the proprietary Mave repo once they got a license.

How about this instead:

To prepare to build JavaMOP, you must either
* Install RV-Monitor to your local Maven repository running
`mvn validate -DrvMonitorBase=<RV-Monitor_HOME>` (no failures should be reported); or
* Get access to the proprietary RV Maven repository (contact RV for that).