Fixing some domain reload tests failing in playmode

List of tests:
	1.	Editor_DomainReload_InputSystemInitializationCausesDevicesToBeRecreated
	2.	Editor_DomainReload_PreservesEnabledState
	3.	Editor_DomainReload_PreservesUsagesOnDevices
	4.	Editor_DomainReload_RetainsUnsupportedDevices

Author: josepmariapujol-unity

Packages/com.unity.inputsystem/Tests/TestFixture/InputTestFixture.cs

@@ -663,7 +663,7 @@ public void EndTouch(int touchId, Vector2 position, float pressure, Vector2 delt
         public void CancelTouch(int touchId, Vector2 position, Vector2 delta = default, bool queueEventOnly = false,
             Touchscreen screen = null, double time = -1, double timeOffset = 0)
         {
-            SetTouch(touchId, TouchPhase.Canceled, position, delta, queueEventOnly: queueEventOnly, screen: screen, time: time, timeOffset: timeOffset);
+            SetTouch(touchId, TouchPhase.Canceled, position, 1, delta, queueEventOnly: queueEventOnly, screen: screen, time: time, timeOffset: timeOffset);
         }
 
         public void CancelTouch(int touchId, Vector2 position, float pressure, Vector2 delta = default, bool queueEventOnly = false,
@@ -1005,7 +1005,9 @@ internal void SimulateDomainReload()
             // have no proper way of simulating domain reloads ATM. So we directly call various
             // internal methods here in a sequence similar to what we'd get during a domain reload.
 
-            InputSystemEditorInitializer.s_SystemObject.OnBeforeSerialize();
+            // Some editor test runs may not have created the system object yet.
+            // Guard against it so domain reload simulation doesn't NRE (NullReferenceException).
+            InputSystemEditorInitializer.s_SystemObject?.OnBeforeSerialize();
             InputSystemEditorInitializer.s_SystemObject = null;
             // InputSystem.InitializeInEditor(runtime);
         }