Brent transition responses

The resource manager, Brent, publishes transition completed responses on the tnco-rm-transition-response Kafka topic to be processed by the orchestration engine Daytona and other applications. The message is in JSON format.

An example message that is published for a Create of a Kubernetes Driver resource instance is (the format is the same for all transitions):

{
   "requestId": "3c271c91-3b9c-4373-979b-fd432587a580",
   "transitionName": "Create",
   "version": "1.0.0",
   "resourceManagerId": "brent",
   "deploymentLocation": "core",
   "resourceType": "resource::dummy-vnfc-dummy::1.0",
   "resourceInstance": { 
      "resourceId": "9665c901-e1ab-4dc1-a298-53742f80cf09",
      "resourceName": "test-dummy__dummy",
      "resourceType": "resource::dummy-vnfc-dummy::1.0",
      "resourceManagerId": "brent",
      "deploymentLocation": "core",
      "metricKey": "12d27542-272d-412d-ae9f-09e8df113137",
      "lastModifiedAt": "2021-08-25T08:52:32.433Z"
   },
      "requestState": "COMPLETED",
      "context": {
         "DRIVER_ASYNC_RESPONSE": "DRIVER_ASYNC_RESPONSE",
         "DRIVER_RPC_RESPONSE": "DRIVER_RPC_RESPONSE"
      },
      "startedAt": "2021-08-25T08:52:34.32Z",
      "finishedAt": "2021-08-25T08:52:34.32Z"
}

Note in particular the internalResourceInstances array, which contains driver-defined topology instances that are related to the parent resource instance. The content of this array is driver-specific. For the Kubernetes driver, see https://github.com/accanto-systems/kubernetes-driver/blob/master/docs/reference/associated-topology.md. Note the terminology that is used in Brent and the drivers is “associated topology” rather than internalResourceInstances. For the OpenStack driver, the associated topology comprises a single entry that contains the OpenStack Stack ID. For example:

{
    "id": "[stack id]",
    "name" "InfrastructureStack",
    "type": "Openstack"
}