eBPF tracing support for python runtime installed using bazel

# 🚀 feature request

### Relevant Rules

My workspace file looks like this

```python
### PYTHON
http_archive(
name = "rules_python",
sha256 = "94750828b18044533e98a129003b6a68001204038dc4749f40b195b24c38f49f",
strip_prefix = "rules_python-0.21.0",
url = "https://github.com/bazelbuild/rules_python/releases/download/0.21.0/rules_python-0.21.0.tar.gz",
)

load("@rules_python//python:repositories.bzl", "py_repositories")

py_repositories()

# use hermetic / bundle python3.9
load("@rules_python//python:repositories.bzl", "python_register_toolchains")

python_register_toolchains(
name = "python3_9",
python_version = "3.9",
register_coverage_tool = True
)

load("@python3_9//:defs.bzl", "interpreter")
load("@rules_python//python:pip.bzl", "pip_parse")

pip_parse(
name = "python_deps",
python_interpreter_target = interpreter,
requirements_lock = "//third_party/python:requirements_lock.txt",
)

# Load the starlark macro which will define your dependencies.
load("@python_deps//:requirements.bzl", "install_deps")
```

### Description

I want to use eBPF to instrument my application.

### Describe the solution you'd like
Its possible to use eBPF if this URL is followed for building python https://docs.python.org/3/howto/instrumentation.html
In addition to this, having frame pointer is also useful, python needs to be built with the `-fno-omit-frame-pointer` option

Commencez par lire les points d’entrée python_register_toolchains et interpreter référencés dans le workspace example, puis comparez leur configuration de build aux exigences d’instrumentation de Python indiquées dans la documentation liée. La tâche est terminée lorsqu’un runtime Python installé via rules_python peut prendre en charge l’instrumentation eBPF et est compilé avec les frame pointers activés.

Rédigé par le modèle d'indexation à partir du texte de l'issue.