Pod level metrics for drop may miss localCtx labels

Describe the bug Consider the following scenario:

Server is running in a pod on node-1 We annotate the server to observe dropped packets Apply a network policy for ingress When a pod on other nodes try to connect to server, the IPTABLE rule on that node will drop the packet. However, for local context, our filter_map won't have the IP of the server, hence we will not generate any event. Thus, we will see drop_count increase at the node level, but no pod level labels for the drops True for external connections as well This is due to how Azure NPM works today. May need to add disclaimer to account for this behavior.

cc @anubhabMajumdar