The test case origin is lost on test result notifications

Current situation

The Notification specification for test results (orchestrator#1 (comment 678441811)) does not keep track of the information source.

If a workflow runs a test more than once, there is no way to tie the notification with the corresponding test execution.

Desired outcome

The Notification specification should be amended to include an .metadata.attachment_origin entry, as is done for WorkflowResult.

The content if this entry is a list of attachment IDs. There must be at least one such ID for each test result notification.

If the .metadata.attachment_origin entry contains more than one ID, each .spec.testResults[] entry must have an additional .spec.testResults[].attachment_origin entry, tying the test result to a given attachment. Those IDs must also be listed in the .metadata.attachment_origin entry.

If .metadata.attachment_origin only contains one ID, each .spec.testResults[] entries may have an additional .spec.testResults[].attachment_origin entry (with the value the one specified in the .metadata.attachment_origin list.

{
  "apiVersion": "opentestfactory.org/v1alpha1",
  "kind": "Notification",
  "metadata": {
    "name": "...",
    "workflow_id": "..."
    "attachment_origin": [
      "db23a450-81ff-4022-a002-b68fd7156490",
      "fe6eea9e-6f6f-49ca-9d5b-a9cfbd35a5c1"
    ]
  },
  "spec": {
    "testResults": [
      {
        "id": "90620e25-d0ae-424d-8873-60394067e10d",
        "name": "test case 123",
        "status": "SUCCESS",
        "attachment_origin": "db23a450-81ff-4022-a002-b68fd7156490"
      },
      {
        "id": "2516d987-9dc6-4e4c-b886-88a19c976d68",
        "name": "test case 453",
        "status": "FAILURE",
        "attachment_origin": "fe6eea9e-6f6f-49ca-9d5b-a9cfbd35a5c1"
      }
    ]
  }
}