⚡ Bolt: Optimize eBPF event parsing (380x speedup)

[blue4209211]

💡 What: Replaced reflection-based binary.Read with manual binary.LittleEndian parsing in the hot eBPF event loop.
🎯 Why: binary.Read is slow and generates significant allocations, causing CPU overhead in high-throughput scenarios (like L7 tracing).
📊 Impact:

• L7Event parsing: ~380x speedup (104,945 ns/op -> ~270 ns/op)
• TcpEvent parsing: ~7x speedup (1,377 ns/op -> ~180 ns/op)
• Allocations reduced from 9KB/op to 0-384B/op.
  🔬 Measurement: Verified with ebpftracer/parsing_test.go benchmarks and correctness tests.

---

PR created automatically by Jules for task 677377576200725842 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.

[gemini-code-assist]

Warning

You have reached your daily quota limit. Please wait up to 24 hours and I will start processing your requests again!

[mayankpande88]

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