PR Summary

Previously, when finding the 3D zorder, external artists were assumed to
use the calling convention of Patch3D.do_3d_projection from Matplotlib
3.3, where it took a positional renderer parameter. This triggered
a deprecation warning, even if the artist could support the new
convention. Now we attempt to bind the signature first, and only emit a
deprecation warning if the calling convention does not appear to work.

PR Checklist

Tests and Styling

• Has pytest style unit tests (and pytest passes).
• Is Flake 8 compliant (install flake8-docstrings and run flake8 --docstring-convention=all).

Documentation

• [N/A] New features are documented, with examples if plot related.
• [N/A] New features have an entry in doc/users/next_whats_new/ (follow instructions in README.rst there).
• [N/A] API changes documented in doc/api/next_api_changes/ (follow instructions in README.rst there).
• [N/A] Documentation is sphinx and numpydoc compliant (the docs should build without error).

Fix #21740.

The original logic this modifies was introduced in #18302, where there was a comment that this was deliberately avoiding signature parsing to make things simpler. However, with the new calling convention only being used if the Artist.__module__ is mplot3d-internal, this meant that library code (e.g. Qiskit/qiskit#7301) could not avoid triggering the deprecation warning, even if downstream Artist did actually fulfill the convention. Since the warnings are triggered during the drawing phase, which may well be outside library control, we couldn't suppress the warnings without changing global user filters.

If the performance hit from using signature.bind is too heavy, it could also do

try:
    return artist.do_3d_projection()
except TypeError as exc:
    # - check the exception stack that the issue was the bind, not raised within the function
    # - do the deprecation warning
    return artist.do_3d_projection(renderer)