Fix conntrack issue and increase supported port/protocol

[jayanthvn]

Issue #, if available: Fixes #100

Description of changes:
Scenarios where ingress is blocked for all pods in two namespaces but there is another policy where ingress is allowed between certain pods in those namespaces then traffic is denied for those pods even if there is a policy to allow when the pods land on the same node. This is because of the way conntrack table was designed. When an entry is made in the conntrack table, we used to add the IP of the pod which created the entry in the value field. Now when both the pods are in the same node then the other pod on receiving the packet will overwrite the value since the key will be same. This would wrongly make the receive pod as the owner of the entry.

As part of this change, we will also increase the number of supported ports and protocol from 8 in IPv4 and 4 in IPv6 to 24 in IPv4 and IPv6.

/opt/cni/bin/aws-eks-na-cli ebpf dump-maps 38
Conntrack Key : Source IP - 192.168.79.164 Source port - 47102 Dest IP - 192.168.76.227 Dest port - 10000 Protocol - 17 Owner IP - 192.168.79.164
Value : 
Conntrack Val -  1
*******************************
Conntrack Key : Source IP - 192.168.93.48 Source port - 44141 Dest IP - 192.168.55.66 Dest port - 10000 Protocol - 17 Owner IP - 192.168.93.48
Value : 
Conntrack Val -  1
*******************************
Conntrack Key : Source IP - 192.168.79.164 Source port - 48336 Dest IP - 192.168.76.227 Dest port - 10000 Protocol - 17 Owner IP - 192.168.79.164
Value : 
Conntrack Val -  1
*******************************

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.