Antrea NetworkPolicy and K8s NetworkPolicy collides if have the same name and namespace

[Dyanngg]

Describe the bug
Between controller and agent, Antrea NetworkPolicy and K8s NetworkPolicy are both converted to internal networkpolicy type for consumption. The keyFunc for the internal np store is defined as 'namespace/name' (L125, pkg/controller/networkpolicy/store/networkpolicy.go). Since both resources are namespaced, K8s NP and ANP with the same name in the same namespace will result in the same key generated for internal networkpolicy, while the spec of those two policies will be different. Hence, the controller will not be able to distinguish a ADD event for a new, same named policy and a UPDATE event for the original policy.

Proposed Solution
#1084 (comment)

[abhiraut]

@tnqn do you have bandwidth to tackle this? or want me to take a crack on it. not sure if you already started work

[tnqn]

@abhiraut I can work on this, I needed this to help distinguish policies for status and stats report.

[antoninbas]

Moving this to the v0.11 milestone as discussed in #1258

[tnqn]

Closed by #1445