More fixes to usePressableState

[Saadnajmi]

Platforms Impacted

• iOS
• macOS
• win32 (Office)
• windows
• android

Description of changes

There are two changes in this PR:

1. Pull in the latest version of react-native-macos that includes some bug fixes with pressable (specifically [0.63] Pull in Pressable onMouseEnter/onMouseLeave changes from #855  react-native-macos#857)
2. Undo part of Support onPress/onLongPress in usePressableState #1061 , where I had the onPress/onLongPress callbacks set the press state. This was a mistake, as only onPressIn/onPressOut should set state. With the code as it was, onPress could fire after onPressOut, set the state {pressed: true}, and our buttons would be stuck in the pressed state even though they aren't being pressed.
3. Makes the public API of useHoverHelper take in onHoverIn/onHoverOut, while mapping it to the Pressable props onMouseEnter/onMouseLeave. This was done because RN Core doesn't actually expose onHoverIn/onHoverOut yet, which we should fix upstream. Our desktop ports (react-native-macos and react-native-windows) expose the similar props onMouseEnter/onMouseLeave, so we should map to that.

Verification

Locally switched some controls (namely button and experimental-button) to use usePressableState instead of useAsPressable and verified that the pressed state was getting set correctly.

Pull request checklist

This PR has considered (when applicable):

• Automated Tests
• Documentation and examples
• Keyboard Accessibility
• Voiceover
• Internationalization and Right-to-left Layouts