Improve "native" component stacks host component frames

React and React DevTools generate component stacks in the same format as native Error stacks. For user components (class and function components) this is done by intentionally causing the component's render method to throw an Error, and then stitching the error stack frames together:
https://github.com/facebook/react/blob/5fa4d79b00988f354073bc27313363dd5cce9cd3/packages/react-devtools-shared/src/backend/DevToolsComponentStackFrame.js#L62-L203

This results in a component stack like this:

But for "host components" (e.g. HTMLDivElement or View) when we have no source location to show, we fall back to showing just "at div" or "at View".

We could probably more closely mirror what JavaScript engines do by appending a "location" like (native) or (unknown location) (as the v8 docs suggest) or (anonymous) as v8 seems to actually do in testing.

The trick would be matching the specific browser/engine's behavior for this. For example, running the following code in Chrome or Node...

JSON.stringify({}, () => console.log(new Error('')));

...will show the stack frame:

    at JSON.stringify (<anonymous>)

while Firefox will show:

Error: 
    <anonymous> file:///path/to/script:7

Improving this format so that host components more closely mirror native Error stacks will help simplify things like React Native's error parsing.

Start in packages/react-devtools-shared/src/backend/DevToolsComponentStackFrame.js, especially lines 62-203, and compare its host-component fallback with the V8 and Firefox examples in the issue. Check how the resulting stack is consumed by React Native error parsing. Done means host frames use an engine-appropriate location format without changing user-component stack behavior.