Add filter to ignore traffic coming from from the agent

[MikeGoldsmith]

Is your feature request related to a problem? Please describe.
We suspect some of the traffic being captured and converted to events is the agent sending events to Honeycomb, eg libhoney sending events. Should the act of sending telemetry cause more telemetry to be generated?

Describe the solution you'd like
Have a way to filter out traffic generated directly by the agent.

Describe alternatives you've considered
We trialed a potential solution in the following PR that used the agent pod's IP in the bpf filter. However, because we use hostnetwork:true in our Kubernetes deployment, the agent's pod IP is the same as the node IP which leads us to filter out more traffic than intended. For example, node->pod health checks and any other service that uses hostnetwork:true.

• feat: Update BPF filter to ignore agent's pod IP #194

Additional context

[JamieDanielson]

To consider as an intermediate: don't add k8s metadata to these events.