#327 rabbitmq connections and #350 track run status

[jeanetteclark]

In this PR:

• add a quartz monitor method to the Controller which runs MonitorJob
  • configurable in metadig.properties
  • checks for runs in the runs table that have a status of processing and a timestamp older than 24 hours
• add a Store method to query for runs with the above criteria (getProcessing)
• add a field to the runs table, runCount, and add it to the Run model
• make the Worker insert a row into the runs table with status processing, and ack the message from the Controller afterwards, before running checks
• minor change to sendAssessmentTest.py to fix a bug and run only a test suite
• bump renjin and solr versions in pom.xml
• a test for the getProcessing method using the in memory store (not that realistic for what we will actually use it for, sadly)
• fixed code formatting

Feedback appreciated - I'm especially not that happy with the pattern for the MonitorJob code that retrieves the object and its system metadata, would love some suggestions there

[jeanetteclark]

Thanks for the review @mbjones - I got most items fixed. Can we discuss the stuff surrounding exceptions more broadly on the backend call tomorrow?

[mbjones]

Sounds like a good plan for tomorrow's call.

[jeanetteclark]

Thanks for the review @mbjones and @artntek. I think at this point I've addressed your comments and fixed up all of the exceptions (in this part of the code anyway). Would you mind having a look again and with your ok we can merge and start moving towards the release