Add a note explaining that the `wheel` requirement that used to be
historically used in documentation was incorrect.  This also explains
why it can frequently be found in existing projects, and what problems
it causes.  I find myself repeatedly explaining it, so I think having
a single official source would be better.

Incorporates suggestions from Anderson Bravalheri.

Before this patch, the documentation suggested the package authors to
declare a fixed set of hooks inherited from setuptools. But this
approach turned out non-future proof. Over time, as `setuptools` added
support for editable installs, it introduced new hooks per PEP 660.
But if one were to follow the outlined example, they'd end up with an
in-tree build backend that does not support editable installs, nor
would it re-export any hooks that might be added in future versions of
setuptools, implementing any new standards that may emerge over time.

This change demonstrates an approach that would allow the thin wrapper
authors to get the new hooks that setuptools may add over time.

Ref: https://github.com/ansible/ansible/pull/79606#discussion_r1080753862

Configured indicates that the function code's itself would be configured, not that it is used by an external party. Switch verb to "used" to be clearer as to how the function is being used.