Bundle updates: dor-workflow-service ~> 2.0, lyber-core ~> 4.0

[dazza-codes]

This updates the master branch to the latest dor-workflow-service and lyber-core. The former could not be upgraded without first upgrading the latter. These upgrades do not seem to require any code changes (although you would think that major version changes could break the prior API); these upgrades on the develop branch were not accampanied by any code changes there either, see:

• lyber-code update: https://github.com/sul-dlss/sdr-preservation-core/commit/f3e9bebb7bb8a8faab2ba48b08504ca7e0014886
• dor-workflow-service update: https://github.com/sul-dlss/sdr-preservation-core/commit/d663b47af20e079dd181f6d59e9ad53a8db9a80f

[jmartin-sul]

not too surprising that the major upgrade on those didn't cause breakage. seems that each had a major overhaul to the internals, but less churn in the user facing API (which i think leaves the decision as to whether it's a major/minor release at the discretion of the project?)

• https://github.com/sul-dlss/dor-workflow-service/releases/tag/v2.0.0 -

  • Replace all RestClient usage with Faraday with persistent HTTP connections (#26)
  • Improved the Dor::WorkflowService abstraction to include methods that dor-services went directly to the HTTP API for (#31)
  • Wrap HTTP and other data exceptions in a generic Dor::WorkflowException, instead of exposing the underlying HTTP client errors.

• https://github.com/sul-dlss/lyber-core/releases/tag/v4.0.0

  • Upgrade to dor-services 5.x
  • Drops LyberCore::Destroyer
  • Cleans up dependencies.

i could see how either of those could actually result in breakage for consumers, depending on how consumers were using the gems?