feat(cli): use LogBox for static Metro errors (#22118)

# Why

Static rendering errors from Metro are hard to use. This PR (in
conjunction with https://github.com/expo/router/pull/491) makes it
p

feat(cli): use LogBox for static Metro errors (#22118)

# Why

Static rendering errors from Metro are hard to use. This PR (in
conjunction with https://github.com/expo/router/pull/491) makes it
possible to use LogBox for all Metro rendering errors.

# Test Plan

<img width="783" alt="Screenshot 2023-04-13 at 1 42 01 PM"
src="https://user-images.githubusercontent.com/9664363/231853560-77062191-47ea-43c4-8f2f-9f366b7e5418.png">
<img width="835" alt="Screenshot 2023-04-13 at 1 42 22 PM"
src="https://user-images.githubusercontent.com/9664363/231853562-48ae2dd7-8aea-46f5-b7d8-f4c222595b21.png">


<!--
Please describe how you tested this change and how a reviewer could
reproduce your test, especially if this PR does not include automated
tests! If possible, please also provide terminal output and/or
screenshots demonstrating your test/reproduction.
-->

# Checklist

<!--
Please check the appropriate items below if they apply to your diff.
This is required for changes to Expo modules.
-->

- [ ] Documentation is up to date to reflect these changes (eg:
https://docs.expo.dev and README.md).
- [ ] Conforms with the [Documentation Writing Style
Guide](https://github.com/expo/expo/blob/main/guides/Expo%20Documentation%20Writing%20Style%20Guide.md)
- [ ] This diff will work correctly for `expo prebuild` & EAS Build (eg:
updated a module plugin).

---------

Co-authored-by: Expo Bot <[email protected]>

show more ...