MotionController / Component enhancement: Separate out updates to visuals and values from gamepad

[DevPika]

The current implementation of Components in motion-controllers package updates both values and visuals inside updateFromGamepad. However, in some cases developers might be interested in updating the components with the latest gamepad values only without computing new Visual Responses, for instance if they are using the library only to send out WebXR controller/gamepad events.

Link to relevant example of a use case (using motion-controllers and three.js)
Link to exact call to package where this would be useful

Suggested improvement: Move the functionality related to updating the Components values from gamepad (L52 to L96) to a separate public method without changing the existing API.