Fix conflicting assertions for click events (facebook#46633)

Summary:
Pull Request resolved: facebook#46633

There is an assertion in the "basic click test" that [checks](https://github.com/facebook/react-native/blob/d6e0bc7/packages/rn-tester/js/examples/Experimental/W3CPointerEventPlatformTests/PointerEventClickTouch.js#L36-L40) that `isPrimary` is set to false. The same assertion suite also does a mouse event [validation](https://github.com/facebook/react-native/blob/d6e0bc7/packages/rn-tester/js/examples/Experimental/W3CPointerEventPlatformTests/PointerEventSupport.js#L201-L204) that `isPrimary` is set to true.

This fixes the conflicting assertions, favoring the behavior observed on Web, that `isPrimary` for mouse click events should be set to false.

## Changelog

[General][Fixed] Fixed issues with W3C PointerEvents tests

Differential Revision: D63336622

packages/rn-tester/js/examples/Experimental/W3CPointerEventPlatformTests/PointerEventSupport.js

@@ -198,8 +198,10 @@ export function check_PointerEvent(
       assert_equals(nativeEvent.height, 1, 'height of mouse should be 1');
       assert_equals(nativeEvent.tiltX, 0, eventType + '.tiltX is 0 for mouse');
       assert_equals(nativeEvent.tiltY, 0, eventType + '.tiltY is 0 for mouse');
-      assert_true(
+      assert_equals(
         nativeEvent.isPrimary,
+        // isPrimary is set to false for 'click' events
+        eventType !== 'click',
         eventType + '.isPrimary is true for mouse',
       );
     }, pointerTestName + ' properties for pointerType = mouse');