Deprecate `reactotron-react-js` and move functionality into `reactotron-react-native`.

At least internally, most uses of Reactotron for web are either Expo web or react-native-web exports of a React Native app.

In Ignite, we need to an awkward re-export of ReactotronClient to get our Reactotron config to work properly https://github.com/infinitered/ignite/blob/master/boilerplate/app/devtools/ReactotronClient.web.ts

reactotron-react-js is not a lot of code, it is:

• a different set of client defaults https://github.com/infinitered/reactotron/blob/master/lib/reactotron-react-js/src/index.ts#L28-L42
• an alternative implementation for trackGlobalErrors https://github.com/infinitered/reactotron/blob/master/lib/reactotron-react-js/src/plugins/track-global-errors.ts

These can be inlined into reactotron-react-native with .web.ts alternatives. This is a more familiar pattern to React Native libraries since Metro handles bundling platform extensions.

Now that we can ship source code in Reactotron and let Metro bundle it, this pattern would be easier to use.

TODO:

• figure out how to handle platform extensions in Rollup bundle.

Start with lib/reactotron-react-js/src/index.ts and lib/reactotron-react-js/src/plugins/track-global-errors.ts, then compare their defaults and behavior with reactotron-react-native. Investigate how Rollup handles the proposed .web.ts platform extensions, and use the existing Ignite ReactotronClient.web.ts re-export as a compatibility case. Done means the web functionality is available through reactotron-react-native and the separate package can be deprecated without breaking that setup.