API change: In EIP_OBJECT_CONNECTION_IND_T, substitute addressing tuple by three actual application paths

In the mentioned packet, we use the tuple (ulClass, ulInstance, ulConnPointOT, ulConnPointTO) as addressing information of the targeted assemblies.

This shall be substituted with three actual application paths (config, production, consumption), where each one consist of the members:

{
  ulClass,
  ulInstance,
  ulAttribute,
  ulMember,
  ulConnPoint,
}

This is more compliant with the CIP specification and now that connection paths are parsed in a more formal fashion and and the applicaion path ordering is properly respected (done with ticket PSEIP-305), it makes sense to extend/rework the API to include this.

This will prepare us for future connection points which are not part of the assembly object, but other objects, e.g. diagnostic connection points.