Use full name for consistency in main definition

TOSCA supports use of full, short and qualified names and in the parser
we have test examples for all. In the main definition file we have mainly
used full name for better readability and to avoid any possible conflict among
types. However there are couple places where definition file has short names
and that did cause confusion among users. These changes are made for consistency
and readability in the defintion file.

Change-Id: If7a8c3bb0e9bd91c811d0795a350b41229015924

toscaparser/elements/TOSCA_definition_1_0.yaml

@@ -671,7 +671,7 @@ capability_types:
       publish_ports:
         type: list
         entry_schema:
-          type: PortSpec
+          type: tosca.datatypes.network.PortSpec
         required: false
         description: >
           List of ports mappings from source (Docker container)
@@ -679,7 +679,7 @@ capability_types:
       expose_ports:
         type: list
         entry_schema:
-          type: PortSpec
+          type: tosca.datatypes.network.PortSpec
         required: false
         description: >
           List of ports mappings from source (Docker container) to expose
@@ -799,7 +799,7 @@ data_types:
         constraints:
           - valid_values: [ udp, tcp, igmp ]
       target:
-        type: PortDef
+        type: tosca.datatypes.network.PortDef
         required: false
       target_range:
         type: range
@@ -807,7 +807,7 @@ data_types:
         constraints:
           - in_range: [ 1, 65535 ]
       source:
-        type: PortDef
+        type: tosca.datatypes.network.PortDef
         required: false
       source_range:
         type: range