It shall be possible to edit the following on a non-normative data type in the UI:

• Description
• Constraints (add/modify/delete)
• Default Value

It shall continue to not be possible to edit

• Name
• Type

The title of the modal shall be "Edit Property" when an existing property is opened rather then "Add Property"

A new endpoint will need to be created on the backend in DataTypeServlet, suggested details

• HTTP method: PUT 
• path: {id}/properties
• method name: updateProperty

The definition of the data type in the additional_types.yaml must be updated to reflect the modifications

Verify:

1. Can edit description
2. Can add constraints
3. Can edit constraints
4. Can remove constraints
5. Can edit default value, verify for string, number, scalar types, complex types, lists maps
6. New values are reflected correctly in the data type UI, even when close and re-open the modal
7. New values are reflected in a node type that uses the data type, i.e where a VFC has a property of the type that has been edited. Should be verified for a property that exists before the data type is edited and a new VFC property created after the data type is edited.
8. New values are reflected in a service that use the data type, i.e.
   a service with a property of the type that has been edited). Should be verified for a service property created before the data type is edited and a property created after the data type is edited
   a service with a VFC instance with a property of the edited type. Should be verified for a property that exists before the data type is edited and a new VFC property created after the data type is edited.
9. The definition in the additional_types.yaml in a service csar for the same model contains the updated definition