doc how to access entry points / bin / scripts from wheels

In a non-bazel venv, distributions make executables available by putting them in `$venv/bin`, which gets added to PATH. In older versions of rules python, py_binary's were generated for these. It isn't obvious how to do similar in the latest versions.

I think the entry-points doc is the relevant part? https://rules-python.readthedocs.io/en/latest/pypi/use.html#entry-points

I suspect the term "entry point", while correct, is too jargon. In [this Slack post](https://bazelbuild.slack.com/archives/CA306CEV6/p1749710911117809), the user described it more in terms of "I want to run a binary from the package".

I'd suggest rephrasing the docs to be use-case oriented in the user's terms, e.g.

* I want to run a binary from a wheel in e.g. `genrule(cmd="$(location )")`
* I want to run a binary from a wheel from another program
* I want a binary to be available on PATH so I can run it like in a normal venv.

Maybe a table that maps non-bazel idioms to bazel idioms would be helpful?

Commencez par la section entry-points de la documentation de rules-python liée dans l’issue. Vérifiez comment elle explique actuellement les binaires provenant de wheels, puis documentez les cas d’utilisation demandés : invoquer un binaire depuis un genrule, l’appeler depuis un autre programme et le mettre sur PATH, éventuellement avec un tableau faisant correspondre les idiomes non-Bazel aux idiomes Bazel.

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