PR summary

This avoids a level of indirection, and also means that aFT2Font is aPyFT2Font (since there are no other subclasses), which helps with some future work. The only downside is that the constructor/destructor order is fixed and slightly different, so we need to split the open/close stages for theFT_Face and explicitly call them inPyFT2Font.

There are currentlystill two copies of the fallback list, one on each level. The one onFT2Font is what's actually used, but the one onPyFT2Font is the actual owner (because pybind11 owns the objects, so we need a Python object to own them). I think it may be possible to drop that extra copy by switching tostd::shared_ptr, but that will likely require the smart holders that are new in pybind11 v3, and I haven't fully tested that out yet.

This PR is based on/waiting for#30322.

PR checklist

• [n/a] "closes #0000" is in the body of the PR description tolink the related issue
• new and changed code istested
• [n/a]Plotting related features are demonstrated in anexample
• [n/a]New Features andAPI Changes are noted with adirective and release note
• [n/a] Documentation complies withgeneral anddocstring guidelines