chore: update react-dev-utils, react-error-overlay

[herecydev]

⚠ No changelog about breaking changes

Testing

Test 1 (wrong import)

import { Link } from "gatsby" => import { Links } from "gatsby"

Before

After

Test 2 (missing react import)

Before

After

import React from "react" => (removed)

[hoobdeebla]

I looked through the commit logs for what Gatsby uses and found these results:

methods used	current version published	updated version published	changes between current and updated versions
react-dev-utils/formatWebpackMessages	2018-10-14	2020-03-21	update error messages, ESLint/typo fixes - none breaking
react-dev-utils/launchEditor	2018-10-14	2020-03-21	additional editors added, Windows fixes - none breaking
react-error-overlay	2017-10-30	2020-03-21	add dark mode, update error messages, ESLint/typo fixes - none breaking

the "breaking" changes I found were all updating devDependencies for testing and making production builds - nothing that impacts the user directly

[herecydev]

Looks like the formatWebpackMessages is called but effectively the results are discarded. I'm not sure what the background is on that one but there's overlap with reportWebpackWarnings and structureWebpackErrors. These leads to some inconsitencies that would be good to address. For example:

Displays a warning without line numbers

And the error overlay isn't helpful:

If you compare that to the "structured webpack errors" in my first few screenshots, they are much clearer and easier to work with.

[LekoArts]

Thanks for the PR!

With #29540, #29588 & #29864 merged updates to the packages are not needed anymore :)