[datamodel-upd][SOL003][VNF-OP-GRANT][ v5.2.1][7.3.2.x.x Test-IDs] Add note...

      "description": "Information about internal VLs that are managed by other entities than the VNFM. See notes 4, 5, 7 and 8.\n",

      "type": "array",

      "items": {

        "description": "This type represents an externally-managed internal VL.\n* NOTE 1: It is only applicable if the externally-managed VL is realized by a secondary container cluster network. It shall\n          not be present otherwise.\n* NOTE 2: A link port is not needed for a VNFC internal connection point connected to a secondary container cluster\n          network.\n* NOTE 3: An example of the network attachment definition resource when the container infrastructure service\n          management is a Kubernetes® instance is a network attachment definition (NAD).\n\n* NOTE 4: In the case that the cloud native template included in the MCIOP describes the set of VNFC instances, an \n          instance of intCp need not be included for each VNFC instance as all instances would contain the same \n          information. It is sufficient to include one intCp for the related CPD. The case of using, for a scalable VDU, a \n          cloud native template in the MCIOP that describes one single VNFC instance is not specified in the present \n          document version\n",

        "description": "This type represents an externally-managed internal VL.\n* NOTE 1: It is only applicable if the externally-managed VL is realized by a secondary container cluster network. It shall\n          not be present otherwise.\n* NOTE 2: A link port is not needed for a VNFC internal connection point connected to a secondary container cluster\n          network.\n* NOTE 3: An example of the network attachment definition resource when the container infrastructure service\n          management is a Kubernetes® instance is a network attachment definition (NAD).\n\n* NOTE 4: In the case that the cloud native template included in the MCIOP describes the set of VNFC instances, an \n          instance of intCp need not be included for each VNFC instance as all instances would contain the same \n          information. It is sufficient to include one intCp for the related CPD. The case of using, for a scalable VDU, a \n          cloud native template in the MCIOP that describes one single VNFC instance is not specified in the present \n          document version\n* NOTE 5: Both \"vnfLinkPort\" and \"netAttDefResource\" attributes can be provided in a \"ExtManagedVirtualLinkData\" to indicate \n          that a single internal virtual link is providing connectivity for both VM-based and container-based VNFCs\n",

        "type": "object",

        "required": [

          "id",