chore(ui-react-native): Migrate Checkbox primitive

[ioanabrooks]

Description of changes

This change:

• migrates the checkbox primitive from react-native example package;
• adds a global storybook decorator and removes all occurences from primitives;
• refactors accessibilityRole for checkbox, heading and label primitives to allow users to specify it, while still providing defaults.

Issue #, if available

Description of how you validated changes

Ran storybook and example app in iOS and android.

Checklist

• PR description included
• yarn test passes
• Tests are updated
• No side effects or sideEffects field updated
• Relevant documentation is changed or added (and PR referenced)

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

[changeset-bot]

⚠️ No Changeset found

Latest commit: 42073f2

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[lgtm-com]

This pull request introduces 2 alerts when merging e5fa956 into 3848ca8 - view on LGTM.com

new alerts:

• 2 for Unused variable, import, function or class

[joebuono]

Nice job! Two global comments:

1. Should this component be named Checkbox or CheckboxField? In the RWA, it's named CheckboxField, but there's also a Checkbox component under the hood.

2. Should we add visual touch feedback based on platform expectations (e.g., material design touch feedback for Android, and iOS human interface guidelines). This could also include hitSlop handling for platform-specific touch target sizes

[ioanabrooks]

Nice job! Two global comments:

1. Should this component be named Checkbox or CheckboxField? In the RWA, it's named CheckboxField, but there's also a Checkbox component under the hood.
2. Should we add visual touch feedback based on platform expectations (e.g., material design touch feedback for Android, and iOS human interface guidelines). This could also include hitSlop handling for platform-specific touch target sizes

1. It should be named Checkbox bc it's not a form component. CheckboxField has validations for form purposes.
2. Yeah I can look into that now, honestly was thinking to defer styling for the theming work, since will have to take a second pass on this anyways.

[calebpollman]

Great work! Let's sync offline about the handling of selected and value, not sure if my initial POC was well thought through in that terms of how those props should interact and the event cycle around them

[lgtm-com]

This pull request introduces 2 alerts when merging 5e7c98e into 3848ca8 - view on LGTM.com

new alerts:

• 2 for Unused variable, import, function or class

[ioanabrooks]

As per offline sync, to have parity with our react web component, th elabel should respond to press events as well as the icon. As follow-up PR, after the Icon primitive is implemented, the Checkbox primitive will be refactored to use a Pressable with Icon and Label.

[lgtm-com]

This pull request introduces 2 alerts when merging 151692d into 3848ca8 - view on LGTM.com

new alerts:

• 2 for Unused variable, import, function or class

[calebpollman]

Let's make sure we clean up the buttonStyle prop and iconButtonStyle when we replace the IconButton

[calebpollman]

Thanks for tackling this @ioanabrooks!

[joebuono]

Great job!