Fix handling of controlled state in toggle-able controls

[rurikoaraki]

Platforms Impacted

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

Description of changes

The hook we use to handle toggle events, useAsToggleWithEvent, does not properly take controlled state into account. In particular it updates its internal state regardless of whether the check state is controlled and doesn't apply state applied from the parent correctly, which means that when its checked state is applied via not toggling the control directly, the state becomes out of sync with that the app believes its state should be.

For example, if a checkbox is meant to be controlled and toggling it fires an event to a parent, the behavior would look like:

1. Click the checkbox: Internal state: checked, visual state: checked, tell parent checkbox is checked
2. Parent tells checkbox it's checked, internal state: checked, visual state: checked
3. Parent tells checkbox it's not checked, internal state: checked, visual state: not checked
4. Click the checkbox: internal state: not checked, visual state: not checked <- bug

Fix is to use the useControllableValue hook to store current checked state, which takes controlled state into account when tracking a boolean's value.

Verification

New test added for the case where a controlled checkbox is inside a Pressable and both can toggle the checked state:

Ensured test above toggles as expected with various configurations of toggling via checkbox as well as external controls (Pressable, the buttons).
Tested uncontrolled checkboxes
Tested switches, toggle button

Pull request checklist

This PR has considered (when applicable):

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