make storybook component (optionally) a wrapper, add a event system to make storybook visible, add initial state support

[ndelangen]

What I did

The idea is to give storybook self-control over if it should be shown or not.

This can be achieved by changing how the StorybookApp behaves: making it a wrapper component.

When the component receives no children, it will auto render, assuming the old behavior, making this change bac kwards-compatible.
When the component receives children, it will render only it's children by default, until a STORYBOOK_OPEN event is triggered on the channel.

The proposal is for all Storybook for ReactNative to move their usage of the StorybookApp to be a wrapper component.

How to test

Please explain how to test your changes and consider the following questions

• Does this need a new example in examples/expo-example?
• Does this need an update to the documentation?

If your answer is yes to any of these, please make sure to include it in your PR.

[changeset-bot]

⚠️ No Changeset found

Latest commit: 30a93fc

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