fix issue #17 - [v4.5.1] fix definition of ExtVirtualLinkData Note2 in SOL002_def.yaml

                Moreover, the identifier of the VIM connection provides scope to the resourceId.

      * NOTE 2:	 A link port is not needed for an external CP instance that exposes a CP in the following cases:

                1)  For a VIP CP directly exposed as an external CP:

                    1.1)  No dedicated IP address is allocated as VIP address, as indicated in the VNFD.

                    1.2)  A dedicated IP address is allocated as VIP address, but the NFVO indicates that no port is needed

                          (createExtLinkPort in VnfExtCpConfig set to false).

                2)  For a VIP CP exposed as an external CP via a floating IP address:

                    2.1)  No dedicated IP address is allocated as VIP address, as indicated in the VNFD, and the VNFC CP

                          associated to the VIP CP is also exposed via a floating IP address.

                1) For a virtual IP CP directly exposed as an external CP:

                  1.1) No dedicated IP address is allocated as virtual IP address, as indicated in the VNFD.

                  1.2) A dedicated IP address is allocated as virtual IP address, but the NFVO indicates that no port is

                        needed (createExtLinkPort in VnfExtCpconfig set to false).

                2) For a virtual IP CP exposed as an external CP via a floating IP address:

                  2.1) No dedicated IP address is allocated as virtual IP address, as indicated in the VNFD, and the VNFC

                      CP associated to the virtual IP CP is also exposed via a floating IP address.

                3) For a VIRTUAL CP exposed as an external CP.

                4) For a VNFC CP exposed as an external CP in a secondary container cluster external network.