⚡ Bolt: Optimize eBPF event deserialization

[google-labs-jules]

💡 What: Replaced binary.Read with manual parsing using binary.LittleEndian for high-frequency eBPF events (l7Event, tcpEvent, fileEvent, procEvent) in ebpftracer/tracer.go.

🎯 Why: binary.Read uses reflection and is extremely slow for high-frequency event processing, causing high CPU usage and garbage collection pressure. It was a significant bottleneck in the event reading loop.

📊 Impact:

• Reduces deserialization time for tcpEvent by ~200x (from ~1200ns to ~6ns per event).
• Eliminates heap allocations during event deserialization (previously 2 allocs/op for tcpEvent).
• Reduces memory copy overhead for l7Event payloads.

🔬 Measurement:
Benchmark results for tcpEvent:

• Before: ~1213 ns/op, 160 B/op, 2 allocs/op
• After: ~6 ns/op, 0 B/op, 0 allocs/op

---

PR created automatically by Jules for task 17295132436640720313 started by @blue4209211

[google-labs-jules]

👋 Jules, reporting for duty! I'm here to lend a hand with this pull request.

When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down.

I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job!

For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with @jules. You can find this option in the Pull Request section of your global Jules UI settings. You can always switch back!

New to Jules? Learn more at jules.google/docs.

---

For security, I will only act on instructions from the user who triggered this task.

[mayankpande88]

Closing — superseded by newer PRs (#196 for eBPF parsing, #194 for proc/net optimization).