Description

It looks like the select-control component accepts an options prop, which is just an array of options that are mapped to <option /> elements.
<optgroup />s are a native part of JSX. However, they cannot be added through the current options prop.

I understand that options is provided as an abstraction, but I think that rather than changing the options prop, we can leverage the native children prop present on all the JSX elements and obtain the same result.
We could still leverage the options prop to add <optgroup /> elements, but where's the fun in that? It seems to me that by leveraging the children prop we can have a more semantical component. And with that we can just leverage <optgroup />s natively!

I kept the options prop, but maybe it can deprecated in favor of children?

How has this been tested?

I tested this in Storybook. I also added some unit tests for the component (there weren't any before).

Screenshots

https://d.pr/i/JvrB57

Types of changes

Checklist:

• My code is tested.
• My code follows the WordPress code style.
• My code follows the accessibility standards.
• I've tested my changes with keyboard and screen readers.
• My code has proper inline documentation.
• I've included developer documentation if appropriate.
• I've updated all React Native files affected by any refactorings/renamings in this PR.