Implement TurboModuleRegistry

[johnf]

This is a super naive implementation. I don't have any native experience.

I based this on the react-native implementation, which falls back to native based on the bridge type.
I remove all the checking code and always fall back to nativemodules.

From what I can tell, we could probably get by just having get always return null;

This was enough to get react-native-vector-icons, which recently got new arch support, to work in storybook.

[codesandbox-ci]

This pull request is automatically built and testable in CodeSandbox.

To see build info of the built libraries, click here or the icon next to each commit SHA.

Latest deployment of this branch, based on commit 98495ac:

Sandbox	Source
react-native-web-examples	Configuration

[necolas]

Hi. I don't think TurboModuleRegistry is appropriate for web, as we don't use turbo modules for that platform. react-native-vector-icons etc should avoid trying to load turbo modules on web. Thanks

[johnf]

@necolas I figured it might be appropriate, given the equivalent exists for NativeModules. No problem, I'll create a PR for react-native-vector-icons