Add SVC port selection used by PowerVC for zoning

Expand "Storage Connectivity group" or "Zoning Policy" (wherever is more appropriate) configuration details and granularity around Target Storage. Today PowerVC connects to the SVC cluster via it's service account, collects the nodes' fabric (FC) connectivity details and uses ALL OF THE AVAILABLE SVC FC node ports connected to the fabric to choose from for creating zone(s) with the VM and storage - in an "Initiator" Zoning Policy mode system port selection used by PowerVC for zoning.
In the case where SVC cluster nodes have more than the minimum (more than 4 per node) ports connected to the fabric, the SVC IO types typically is segregated among the ports for proper SVC load balance and traffic isolation - a set of the SVC ports are dedicated for Host IO, storage back-end , a set dedicated for SVC cluster inter-node communication, set dedicated for SVC replication.

PowerVC today randomly or in a round-robin fashion selects any of all of the fabric connected SVC's node ports to zone with VMs without consideration SVC port traffic type designation, ending up creating zones with SVC target ports dedicated for non Host based IO traffic and violating the port designation customer policy.

Example PowerVC LPARs are zoned with set of SVC target ports which the customer have dedicated for SVC Cluster inter-node IO only or SVC to storage back-end only IO.