build: bump pyroscope/ebpf fork for CPython 3.14 support

[gecube]

Draft — blocked on coroot/pyroscope#3.
The Python 3.14 offsets live in the pyroscope eBPF fork. This PR just bumps the replace pin so node-agent picks them up. It's temporarily pinned to the PR branch commit; once coroot/pyroscope#3 merges I'll repoint it to the coroot/pyroscope commit and mark ready.

What

Python 3.14 processes aren't profiled today: the eBPF Python unwinder (from github.com/grafana/pyroscope/ebpf, replaced with the coroot/pyroscope fork) has no offset table for 3.14, so GetUserOffsets returns unsupported version and no profiles are produced. Reported in #318.

This bumps the fork pin to the commit that adds the CPython 3.14 offset table:

-  github.com/grafana/pyroscope/ebpf => github.com/coroot/pyroscope/ebpf v0.0.0-20260413145227-9cce3f956c8e
+  github.com/grafana/pyroscope/ebpf => github.com/gecube/pyroscope/ebpf v0.0.0-20260706122038-22b69c8c6af6

(pyroscope-side change: coroot/pyroscope#3)

Verification

• go mod tidy clean; go build ./profiling/ and go vet ./profiling/ pass with the bumped dependency.
• Runtime A/B against a live python:3.14.6 process (same PID), eBPF session with PythonEnabled:
  • before: pyperf get python process data failed err="unsupported python version ... {3 14 6}"
  • after: pyperf process profiling init success ... Version:{Major:3 Minor:14 Patch:6}

Before marking ready

• feat(ebpf/python): add CPython 3.14 offsets pyroscope#3 merged
• repoint replace from the gecube fork commit to the coroot/pyroscope commit
• go mod tidy

Fixes #318.