Improve OR to TAPI XPDR node mapping

The conversion of an XPDR device into TAPI node has a mistake. The eODU nep should be generated based on the CLIENT ports of the XPDR. At this moment it is based on the NETWORK port. This is wrong becase the eODU represents the LO_ODU and the iODU represents the HO_ODU, meaning that the iODU could aggregate the traffic from multiple LO_ODU.

To cope with the implementation of T0 Multilayer Topology, the SIP of the eODU is moved to the iODU.

The corresponding modifications in the Topology and Connectivity services are also adressed here