Fix issues with robots using the latest dor-services

Also update jhove-service gem

Update to use latest jhove gem

v3.2.4

bump version to v3.2.4

Update to latest dor-services gem

v3.2.3

v3.2.3

v3.2.2

• 96afbcc update version of dor-services gem
• 45a05b3 upgrade to dor-services 5.10.0
• 28ef64c Update travis build matrix
• d420650 config/deploy/dev.rb: remove non-existent hosts
• 736cd4a update to current latest dor-services (5.8.2)

fix embargo_release

embargo_release fixed by:

• upgrade to dor-services 5.8.1 from 5.8.0
  also:
• added tests for embargo_release script

upgrade from dor-services 5.7.0 to 5.8.0, deployment nicety

upgrade dor-services so that common-accessioning is able to use the current supported configuration for interacting with SDR and workflow services (via clients in dor-services talking to the dor-services-app proxy).

also, have the cap script prompt for the branch to be deployed. default to the branch of the current working directory.

v3.1.1

Update Solr field names to match the latest index.

v3.1.0

• use dor-services 5.7.0 (was 5.5.3), specifically for:
  • return an empty FileGroupDifference when contentMetadata is missing.

v3.0.6

• common-accessioning is on all 5 robot VMs (7dd973e)
• Add basic accession robots class that provides the correct wiring for the workflow service (829ea83)
• adds a Robots::DorRepo::Dissemination::Base for workflow_service method and trivial spec to ensure all robots boot
  (15b5dec)

v3.0.5

• bump dor-services to 5.5.3 (adc1c92)
• Use workflow client from Dor::Config (2fe9880)