[test] Run tests periodically with react@next

[eps1lon]

Runs test_unit, test_browser and test_regression once a day with reacts next release channel.

More info in https://reactjs.org/blog/2019/10/22/react-release-channels.html

Why we can't just yarn install react@next:

1. In a monorepo it isn't trivial (with yarn v1) to bump a version
2. enzyme's adapter has a dependency on react-test-renderer (which has a dependency on scheduler) and I'd rather not find out what happens if different versions are used.

Bonus:
This also allows running the pipeline with other release channels like experimental. This might be more interesting once CircleCI allows builds using their 2.1 config via API.

@oliviertassinari Could you change the required status checks accordingly?

-test_unit
+test_unit-1
-test_browser
+test_browser-1
-test_regression
+test_regression-1

[mui-pr-bot]

No bundle size changes comparing 02ac04f...8dd3b49

Generated by 🚫 dangerJS against 8dd3b49

[oliviertassinari]

Nice, it follows suite on vercel/next.js#9151 :)

[oliviertassinari]

How do we know if a build fails with a React canary version? Should we periodically remember to have a look at the build history?

[eps1lon]

I get mails for failed builds