Introduce per-interpreter code ownership

[rogercoll]

Profiler runtime interpreters are highly specific to each language. To support them, one must understand how to unwind the runtime’s stack at the C level. While the maintainers are familiar with most current interpreters, we’re eager to expand support to as many languages as possible. For example, see the BEAM (Erlang/Elixir) support effort: #958

Because stack unwinding requires deep technical expertise for each runtime, I propose assigning a team code owner for each interpreter (repo approvers by default).
While maintainers and approvers will retain final approval rights, code owners will automatically be notified when changes affect their interpreter. This ensures we can gather feedback from those with the most in-depth knowledge of each language’s runtime.

This approach aligns with practices in other OpenTelemetry projects that span multiple areas of expertise: https://github.com/open-telemetry/opentelemetry-collector-contrib/blob/main/CONTRIBUTING.md#becoming-a-code-owner