[DevTools] Global console log

[bvaughn]

Builds on top of #21889.

Console logs are currently scattered and confusing (e.g. double rendering may show logs twice, logs printed before a component suspends may appear to be truncated unexpected and then later printed again when retrying). Overall the sequence of logs in the console can be confusing.

The DevTools backend should collect logs during render (and double render) store them until commit. Then it should ordered semantically (by components position within the tree), de-duplicate them (to remove double renders or Suspended/interrupted renders), and send them to the front-end along with metadata about the commit (e.g. commit priority).

The front-end could print these in a new Log view. Each commit could be grouped (with diver lines between). Clicking on a log in the console could select the component that logged it in the tree (if it's still mounted).

Note that objects logged should not be retained but should be stringified to avoid causing memory leaks. (As a result, de-duplication may not perfectly match browser behavior.) Sending logs to the front-end will most likely require adding new information to the serialized tree update that gets sent after each commit.

[stale]

This issue has been automatically marked as stale. If this issue is still affecting you, please leave any comment (for example, "bump"), and we'll keep it open. We are sorry that we haven't been able to prioritize it yet. If you have any new additional information, please include it with your comment!

[github-actions]

Closing this issue after a prolonged period of inactivity. If this issue is still present in the latest release, please create a new issue with up-to-date information. Thank you!