Investigate eBPF Support

[XAMPPRocky]

We've talked around what eBPF might look like a few times now, so this is a tracking issue for looking into what it would take to support it. The main potential benefit of having higher throughput through removing syscalls and providing process separation from the update configuration and latency tasks for the game traffic.

Requirements

• This added as an additional "mode" to quilkin, similar to agent, manage, and relay. We might add the mode as command under proxy (e.g. quilkin proxy ebpf) to be able to reuse the arguments from proxy, but in code, it would be a separate path, and probably closer to agent in how it works.
• The eBPF still supports dynamic configuration like proxy does. How it pulls that configuration will obviously be different.
• The eBPF filter still supports most of the filters, it doesn't need to support all, as there are some that could never work in the eBPF context, but it still needs to be enough that it is useful for production deployments.