More useKeyProps followup

[Saadnajmi]

Platforms Impacted

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

Description of changes

This PR makes a few changes, ordered in rough importance:

1. Don't specify keyDownEvents and keyUpEvents on Windows

• This matches the behavior before Better types and tests for useKeyProps #2468 merged. As it turns out, Windows specifies handled keyboard events slightly differently: keyUpEvents/keyDownEvents check code, not key react-native-windows#11049 . While that discrepancy exists, let's just not specify the array.

2. Fix mismatched macOS type

• I had accidentally swapped the macOS and base type files for useKeyProps.types.ts. Simple swap back to fix.

3. Refactor the tests to call the hook inside a component

• This is closer to how the hook is meant to be used, so I thought that should be a good change.

4. Move deprecated useKeyCallback to bottom of file.

• This is just to make it more clear it's deprecated and not used for anything else.

Verification

(how the change was tested, including both manual and automated tests)

Before	After
Screenshot or description before this change	Screenshot or description with this change

Pull request checklist

This PR has considered (when applicable):

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