Fix pose unlock smooths in wrong coordinate space

[FejZa]

Reality Collective - Reality Toolkit Pull Request

Overview

• Turns out the source pose reported to the IControllerPoseSynchronizer is in the rigs local space and not world space. This caused issues when smoothing the visualizer pose from the interactable lock pose to the actual controller pose when the player rig is not located at the scene origin. Also I realized we do not need an extra IControllerVisualizer.SourcePose property that was recently introduced, since we can simply use IControllerVisualizer.Controller.Pose for that

• Introduced IInputRig. Same concept as with the locomotion service. The input service expects an IInputRig to be available in the scene so the input service components, such as controllers, can work. The toolkit's player package is a first party citizen and comes with an out of the box input rig, which is the player rig itself. If, for whatever reason, someone decides to use the input service without the player package, then they have to make sure to register the IInputRig manually using their own implementation. This is a very advanced use case scenario though. For testing I have already replaced some of the Camera.main references in the core module using the new InputService.InputRig API. I'll do another PR updating the rest. Resolves RFI: The Input System is unable to operate without a specific camera setup, currently managed by a dependency? #77