Finish updating action mapping files for new action set

[drouin-simon]

Since commit 2c547ca, SlicerVR no longer relies on action mapping files defined in VTK and copied over (CMake code here). It defines its own actions and has its own mapping files (files in VirtualReality/Resources/Bindings, and cmake code here. However

• The new action set is only mapped for the Occulus Quest (vtk_openxr_binding_oculus_touch_controller.json)
• The action mapping files are still copied over from VTK which results in the extension containing two sets of action mapping files, one of which is not being use, which can be confusing.

TODO:

• Port mapping file for other headsets to the new action set
• Remove the code that copies VTK action mapping files to the extension

[lassoan]

Port mapping file for other headsets to the new action set

We'll do similar changes to other headsets as we did for the Meta Quest 3. We cannot those changes without access to the hardware, but we can fix any specific errors that users report.

Remove the code that copies VTK action mapping files to the extension

Those json files are copied as part of the build process, by VTK makefiles. We'll see if we can delete them cleanly with an extra build step or we can make installation of these files in VTK optional.