Patch console to append component stacks

[bvaughn]

• [x] Auto-append component stack to console.error and console.warn calls.
• [x] Temporarily disable all console logging before re-running a function component to inspect hooks.
• [x] Make sure not to double append a stack to any warnings logged by React.
• [x] Test with multiple renderers First injected renderer wins; console won't be patched for subsequent renderers

Resolves #347

Related React PR https://github.com/facebook/react/pull/16133

Questions

• Is the zero width space character (added in 6a196fd) reasonable or might it cause problems with any instrumented logging of warnings/errors? This is out of DevTools hands since the component stack formatting is now being injected by React.
• Is it okay to log owner stacks rather than full component stacks? Seems preferable to me, but it is different from the React official errors/warnings.

Demo

[bvaughn]

CI is failing because of a Yarn issue, https://github.com/yarnpkg/yarn/issues/7403

[bvaughn]

At this point, the tests are expected to fail until https://github.com/facebook/react/pull/16139 has landed. This dependency has been removed.

[bvaughn]

I'm going to go ahead and make this a configurable preference, at least for now. It seems pretty invasive and might turn out to be annoying in ways I haven't accounted for.

[bvaughn]

I'm going to roll forward with this, since there didn't seem to be any strong concerns (just questions). Please feel free to follow up with me if there are concerns though.