chore: Clean up dependencies of apps dependent on the common-app

[MatiPl01]

Summary

This PR moves common-app dependencies to the common-app package.json and removes all of duplicate dependencies from fabric-example, web-example and macos-example apps. We can do this thanks to react-native.config.js which reads all dependencies from the common-app/package.json and adds them to the dependency list from the current app's package.json file (if they weren't specified in the app's package.json).

Some dependencies, which are used in package.json scripts to e.g. start the app, such as react-native, must be added explicitly in each app's package.json.

Motivation

I think it is a bit cumbersome to repeat dependencies needed by the common-app in every app that imports application from the common-app sources. Since every app would need dependencies that common-app needs to work, we don't have to repeat them in every app dependent on the common-app.

If we will have to use a different dependency version or mock a dependency, we can always add another dep e.g. in the fabric-example package.json or exclude/include it in the react-native.config.js.

Test plan

Build the fabric-example / web-example / macos-example to see that everything still works.

[tjzel]

I like the idea but I'm not certain if this is going to work with macos-example (and possible tvos-example in the future) since they might need to be behind in versions etc.

Does it work with macos-example?

[MatiPl01]

I like the idea but I'm not certain if this is going to work with macos-example (and possible tvos-example in the future) since they might need to be behind in versions etc.

Does it work with macos-example?

I updated the macos-example as well. I also implemented your suggestions and added a possibility to override dependencies specified in common-app - this was needed for the macos-example where we use different version of react-native.

The final implementation works in this way:

• if the dependency is not specified in the package.json of the current example app, the dependency from the common-app will be used instead,
• if the same dependency is specified in the current app and the common-app, the current app dep has higher priority and this dependency will override the one specified in the common-app

[tjzel]

Looks good now!