feat: add WebXR helper component

[munozco]

Context:
I want to make a trame-vtk widget to support WebXR in Trame.
Here's the trame-vtk PR: Kitware/trame-vtk#81

This PR:

• changes vtk.js version from 29.4.5 to 32.2.0 to benefit from the WebXR helper. Ideally, the new vtk.js version should include this small fix: fix(webxr): remove controllers rays when stopping XR vtk-js#3220
• adds a new vue component that enables VtkView and VtkSyncView to be used for a WebXR session.

This component is a wrapper for vtk.js' vtkWebXRRenderWindowHelper. It has two methods startXR and stopXR and can trigger enterXR and exitXR events. drawControllersRay can be set to true to draw rays to represent the controllers.

To make the WebXR view work with a VtkView, I had to comment a line in ClientView (last commit). I don't really understand what it does and I get the same results with and without it. @jourdain : do you know what's the purpose of the "Cube axes" section ? I don't understand why it's there since its visibility is always false and it makes the WebXR helper mess with the transform matrix...

[jourdain]

Thanks for doing that and I see the issue.

So the cubeAxes can be turned on by a property. Maybe you can delay the binding of the camera when that prop get turned on?

[munozco]

I can't see anything related to this property, so I added a setCubeAxesVisibility function with a watch on props.showCubeAxes.
This way, we can properly enable or disable the cubeAxis with setCubeAxesVisibility. Should I also add a set_cubes_axis_visibility function in my trame-vtk PR ?

[jourdain]

I think that looks good to me. No need to worry about trame-vtk for now. Thanks for fixing that oversight.

[jourdain]

🎉 This PR is included in version 3.3.0 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀

[finetjul]

shouldn't you call setCubeAxesVisibility to avoid code duplication