fix(deps): set react resolution

[KaiVandivier]

After the previous change in #619, there is still an infinite loop, but it looks different.

One hypothesis is that there is still a circular dependency causing this, which could be between the app-platform and UI, as mentioned in the platform DevEx meeting. Another hypothesis is that a failure to resolve a dependency could cause the infinite loop, which is mentioned in an NPM bug report. The last time, it could have been a failure to resolve a @dhis2/cli-app-scripts version; this time, it could be a failure to resolve a react and react-dom version -- here's some logs that make me think so:

2383 silly placeDep node_modules/@dhis2/cli [email protected] OK for: @dhis2/[email protected] want: ^16.8.6
2384 silly placeDep node_modules/@dhis2/cli [email protected] REPLACE for: [email protected] want: ^16.14.0
....
2455 silly placeDep node_modules/@dhis2/cli [email protected] REPLACE for: @dhis2/[email protected] want: 16.8
2456 silly placeDep ROOT [email protected] OK for: @dhis2/[email protected] want: 16.8
2457 silly placeDep ROOT [email protected] OK for: [email protected] want: ^16.0.0

My hope is that setting a resolution field for a specific react and react-dom version will override the conflicting dependency requirements 🤞

Result update: It did not

[dhis2-bot]

🎉 This PR is included in version 4.2.5-alpha.2 🎉

The release is available on:

• npm package (@alpha dist-tag)
• npm package (@alpha dist-tag)
• npm package (@alpha dist-tag)
• npm package (@alpha dist-tag)
• npm package (@alpha dist-tag)
• npm package (@alpha dist-tag)
• GitHub release

Your semantic-release bot 📦🚀