Add pod metadata in vpc cni network policy manager logs

**What would you like to be added**:
- Add pod metadata in AWS vpc cni network policy manager logs
```
{"level":"info","ts":"2025-04-17T18:08:21.960Z","logger":"ebpf-client","caller":"events/events.go:191","msg":"Flow Info: ","Src IP":"10.152.50.234","Src Port":38940,"Dest IP":"10.152.49.161","Dest Port":8080,"Proto":"TCP","Verdict":"DENY"}
{"level":"info","ts":"2025-04-17T18:08:23.018Z","logger":"ebpf-client","caller":"events/events.go:191","msg":"Flow Info: ","Src IP":"10.152.50.234","Src Port":38940,"Dest IP":"10.152.49.161","Dest Port":8080,"Proto":"TCP","Verdict":"DENY"}
```

**Why is this needed**:
- When I enable Networ policy feature for VPC CNI, Network policy manager emits above logs. Logs have data on Source and Destination IP address.
- However, when a pod gets deleted and a new pod is deployed, same ip address can be assigned to different pod and this makes troubleshooting harder.

Start at the network policy manager log entry shown as events/events.go:191 and trace how the flow information is assembled. Determine which pod metadata can be included to distinguish pods that reuse an IP address. Done means the relevant logs identify the source and destination pods in addition to their network details.

Written by the indexing model from the issue text.