fix a bug in getting netpol connections from rule with named port and protocol

[shireenf-ibm]

currently, if a netpol rule contains a named-port + a protocol name;
the named-port is converted to its port number in the dst pod without checking if both rule's protocol and pod's protocol (for the relevant port) are equal too - which might result a wrong output

example with the error :
suppose having pod-a with following named-port :

- name: newport
   containerPort: 8956
   protocol: SCTP

and a netpol capturing this pod-a with an ingress rule (from any other pod (e.g. new-pod)) with following ports:

    ports:
    - port: newport
      protocol: UDP

in the result we would see a wrong connection to the pod :
helloworld/new-pod[Deployment] => helloworld/pod-a[Deployment] : UDP 8956

while actually there is no match between the rule's port and the pod's named-port, and we shouldn't see a connection.

example files:
netpol.yaml.txt
pods.yaml.txt