Use Metro support for auto-collapsing internal stack frames

[motiz88]

Summary:
Changes ExceptionsManager to respect the collapse field in each symbolicated stack frame returned from Metro, in preference to the client-side regex. This is ultimately driven by a Metro config option (now also set in the RN new project template). Note that the client-side regex is intentionally ignored for any frame where collapse is present ( = all of them if using Metro with facebook/metro#435).

Also updates the client-side regex to match the new renderer paths.

This is part of a redesign of work done originally in #24662; I intend to eventually remove the client-side regex from RN.

Reviewed By: cpojer

Differential Revision: D16500277

[pull-bot]

	Messages
📖	📋 Missing Summary - Can you add a Summary? To do so, add a "## Summary" section to your PR description. This is a good place to explain the motivation for making this change.
📖	📋 Missing Test Plan - Can you add a Test Plan? To do so, add a "## Test Plan" section to your PR description. A Test Plan lets us know how these changes were tested.
📖	📋 Missing Changelog - Can you add a Changelog? To do so, add a "## Changelog" section to your PR description. A changelog entry has the following format: [CATEGORY] [TYPE] - Message. CATEGORY may be: General iOS Android JavaScript Internal (for changes that do not need to be called out in the release notes) TYPE may be: Added, for new features. Changed, for changes in existing functionality. Deprecated, for soon-to-be removed features. Removed, for now removed features. Fixed, for any bug fixes. Security, in case of vulnerabilities. MESSAGE may answer "what and why" on a feature level. Use this to briefly tell React Native users about notable changes.

Generated by 🚫 dangerJS against 015c9d3

[elicwhite]

Should we be hiding this by default but let people override it here?

[motiz88]

Yes. There was some discussion on the RN Discord but I didn't get around to making the changes today. The basic idea is to put the defaults in the CLI, where there's precedent for this kind of thing, rather than in the template.

[react-native-bot]

This pull request was successfully merged by @motiz88 in 77125a1.

^{When will my fix make it into a release? | Upcoming Releases}