Adding ability to update a manifest with details from the DLCS

[JackLewis-digirati]

Resolves dlcs/protagonist#174

This PR makes it so that manifests are updated from the background handler after they've been completed in the DLCS.

There is 3 new DLCS settings, which are as follows:

"DLCS": {
    "OrchestratorUri": "https://dlcs.digirati.io",
   "ManifestNamedQueryName": "batch-query" // defaults to this
   "OrchestratorDefaultTimeoutMs": 3000 // defautls to this
  }

OrchestratorUri is the base address of the orchestrator and ManifestNamedQueryName is the name of the named query used to retrieve images for a manifest

On top of this, there is an SQS setting for listening to the batch completion queue, and the background handler needs access to the storage bucket:

"AWS": {
    "SQS": {
      "BatchCompletionQueueName": "dlcsspinup-batch-completion-presentation"
    },
    "S3": {
      "StorageBucket": "dlcsspinup-presentation-storage"
    }
  }

Additionally, there is a small change to paintedResource to fill out an asset with an assetId as opposed to canvasPainting. i.e.:

"paintedResources": [
        {
            "type": "PaintedResource",
            "canvasPainting": {
                "canvasId": "https://localhost:7230/26/canvases/w0kyujrecuowii23cztsb3",
                "canvasOrder": 0,
                "thumbnail": "https://dlcs.digirati.io/thumbs/26/18/testAssetByPresentation/full/200,115/0/default.jpg",
                "staticWidth": 6932,
                "staticHeight": 3982
            },
            "asset": {
                "assetId": "https://api.dlcs.digirati.io/customers/26/spaces/18/images/testAssetByPresentation"
            }
        }
    ]