Initialise ICAv2 Data Copy Manager

[alexiswl]

Centralised service for copying data around with ICAv2 Jobs, uses taskTokens for 'synced' events (inside AWS Step Functions).

For example an event might look like

{
  "EventBusName": "OrcaBusMain",
  "Source": "Whatever",
  "DetailType": "ICAv2DataCopySync",
  "Detail": {
    "payload": {
      "sourceUriList": [
        "icav2://project-id-or-name/path-to-data.txt",
        "icav2://project-id-or-name/path-to-folder/"
      ],
      "destinationUri": "icav2://project-id-or-name/path-to-destination/"
    },
    "taskToken": "your-task-token"
  }
}

Or

{
  "EventBusName": "OrcaBusMain",
  "Source": "Whatever",
  "DetailType": "ICAv2DataCopy",
  "Detail": {
    "payload": {
      "sourceUriList": [
        "icav2://project-id-or-name/path-to-data.txt",
        "icav2://project-id-or-name/path-to-folder/"
      ],
      "destinationUri": "icav2://project-id-or-name/path-to-destination/"
    }
  }
}

One can generate the Detail from the source with the following AWS StepFunctions Code

{
  "QueryLanguage": "JSONata",
  ...
  "States": {
    "Copy Files to Destination": {
      "Type": "Task",
      "Resource": "arn:aws:states:::events:putEvents.waitForTaskToken",
      "Arguments": {
        "Entries": [
          {
            "Detail": "{% $merge(\n  [\n    {\n      \"taskToken\": $states.context.Task.Token\n    }, \n    $copy_event_detail\n  ]\n) %}",
            "DetailType": "ICAv2DataCopy",
            "EventBusName": "OrcaBusMain",
            "Source": "Whatever"
          }
        ]
      },
      "Next": ...
    }
  }
}

[victorskl]

Please on hold merge this PR until 0.3.0 release wrap up.

[victorskl]

Depends on task token that implemented in #789

[alexiswl]

Depends on task token that implemented in #789

Ah not quite, this one would have its own task token management system, #789 was for workflow events specifically

[victorskl]

Similarly to this PR as well. ditto related conclusion comment here.

Please set PR Ready; once finalised. Thanks.