fix(Prefabs): provide correct axis number for oculus controller

The axis number used on the Oculus Controller was incorrect and
therefore causing the incorrect output when a different part of
the controller was interacted with. This has now been rectified.

Author: extendreality

Runtime/Prefabs/ControllerMappings/Input.UnityInputManager.Oculus.TouchLeftController.prefab

@@ -531,7 +531,7 @@ GameObject:
   m_Component:
   - component: {fileID: 4933412265285294678}
   m_Layer: 0
-  m_Name: Input.UnityInputManager.WindowsMixedReality.LeftController 1
+  m_Name: Input.UnityInputManager.Oculus.TouchLeftController
   m_TagString: Untagged
   m_Icon: {fileID: 0}
   m_NavMeshLayer: 0

Runtime/Prefabs/ControllerMappings/Input.UnityInputManager.Oculus.TouchRightController.prefab

@@ -163,7 +163,7 @@ MonoBehaviour:
     m_TypeName: Zinnia.Action.FloatAction+UnityEvent, Zinnia.Runtime, Version=0.0.0.0,
       Culture=neutral, PublicKeyToken=null
   equalityTolerance: 1e-45
-  axisName: Tilia.Input.UnityInputManager_Axis15
+  axisName: Tilia.Input.UnityInputManager_Axis5
   multiplier: 1
 --- !u!114 &5643188553823536100
 MonoBehaviour:
@@ -934,7 +934,7 @@ GameObject:
   m_Component:
   - component: {fileID: 3857693711571079995}
   m_Layer: 0
-  m_Name: Input.UnityInputManager.Oculus.RightTouchController
+  m_Name: Input.UnityInputManager.Oculus.TouchRightController
   m_TagString: Untagged
   m_Icon: {fileID: 0}
   m_NavMeshLayer: 0

Runtime/Prefabs/ControllerMappings/Input.UnityInputManager.XboxController.prefab

@@ -326,7 +326,7 @@ GameObject:
   m_Component:
   - component: {fileID: 5747361586587986246}
   m_Layer: 0
-  m_Name: Input.UnityInputManager.XBoxController
+  m_Name: Input.UnityInputManager.XboxController
   m_TagString: Untagged
   m_Icon: {fileID: 0}
   m_NavMeshLayer: 0