PyVista <-> Trame integration

[banesullivan]

Quick heads up: the PyVista <-> Trame integration that previously lived inside the main PyVista repository has been extracted into its own standalone package,trame-pyvista and the previous trame implementations will be deprecated in PyVista v0.49, per pyvista/pyvista#8625

Everything has been migrated there with full git history: PyVistaLocalView, PyVistaRemoteView, PyVistaRemoteLocalView, plotter_ui, the Jupyter backends (trame/server/client/html), and the export_html/export_vtksz helpers. PyVista discovers it automatically via entry points, so no code changes are needed by end-users, just install it alongside PyVista. Old pyvista.trame.* imports still work via a thin deprecation shim.

Why we split it out:

• Independent release cycle, so Trame/VTK updates can ship without waiting on a full PyVista release
• Smaller surface area, easier to review, easier to contribute to
• Issues and PRs land in one focused repo instead of getting buried in the much larger PyVista tracker
• Lower barrier for folks who want to hack on the Trame side specifically

I have ensured that the @pyvista/kitware team has access to this new repository but let me know if there are other people that should be added to that team to help maintain this trame package. I'd love to grow a small group of maintainers who care about this PyVista <-> Trame integration and can help drive it forward without being bogged down by the bigger efforts in the main PyVista repository.

[jourdain]

Thanks for isolating it. It will indeed make thing simpler to track and improve.