[cli] fix js inspector is broken when using web SSG (#23197)

# Why

when web SSG is enabled, pressing `j` to open js inspector is broken:
```
Opening JavaScript inspector in the browser...
Web

[cli] fix js inspector is broken when using web SSG (#23197)

# Why

when web SSG is enabled, pressing `j` to open js inspector is broken:
```
Opening JavaScript inspector in the browser...
Web Bundling complete 4499ms
Web Bundling complete 4524ms
FetchError: invalid json response body at http://192.168.50.38:8081/json/list reason: Unexpected token < in JSON at position 0
FetchError: invalid json response body at http://192.168.50.38:8081/json/list reason: Unexpected token < in JSON at position 0
```

# How

originally we have #21068 fix for the HistoryFallbackMiddleware. the new middleware for SSG unfortunately does not have the fix.
i feel like the root cause is coming from middleware disorder. digging the code in deep, i found we've chained the `connect` app. the `middleware` returned from `Metro.createConnectMiddleware` is actually a connect app, because rn-cli will set the `enhanceMiddleware` and it creates the `connect` app under the hood.

this pr tries to reuse the connect app. without the connect app chaining, those web middlewares will be placed after the inspector proxy middleware.

also removed the #21068 hack for HistoryFallbackMiddleware in this pr.


# Test Plan

```
$ yarn create expo -t tabs@sdk-49 sdk49tabs
$ cd sdk49tabs
$ npx expo start
# press `j`
```

after the fix, i've checked:
1. press `j`
2. check `http://localhost:8081/json/list` returns an array
3. check `http://localhost:8081/helloweb` returns a html content
4. disable SSG (the `"output": "static"` in **app.json**), check `http://localhost:8081/helloweb` returns a html content

show more ...

fix(cli): Add fallback error for static rendering (#23170)

# Why

If you attempt to static render without Expo Router then things could go
wrong, this adds a fallback error message in development

fix(cli): Add fallback error for static rendering (#23170)

# Why

If you attempt to static render without Expo Router then things could go
wrong, this adds a fallback error message in development to try and make
things more clear.

<!--
Please describe the motivation for this PR, and link to relevant GitHub
issues, forums posts, or feature requests.
-->

# Test Plan

- In a project without Expo Router (`@expo/metro-runtime`), enable Metro
web and static output, then add an import error.

---------

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

show more ...

feat(cli): Add metro favicon middleware (#23072)

# Why

- Expo Webpack had support and this was a nice feature.

<!--
Please describe the motivation for this PR, and link to relevant GitHub
is

feat(cli): Add metro favicon middleware (#23072)

# Why

- Expo Webpack had support and this was a nice feature.

<!--
Please describe the motivation for this PR, and link to relevant GitHub
issues, forums posts, or feature requests.
-->

# How

- Add middleware in development for `/favicon.ico` which generates a
favicon based on the config in `app.json` `web.favicon`

<!--
How did you build this feature or fix this bug and why?
-->

# Test Plan

- Added tests. They're not fully exhaustive and don't cover the `single`
export case.


<!--
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 `npx expo prebuild` & EAS Build
(eg: updated a module plugin).

---------

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

show more ...

refactor(cli): avoid changing required dependency versions when prebuilding (#23146)

# Why

In the past, we've had issues with bugfixes and minor bumps causing
issues in user projects, without us

refactor(cli): avoid changing required dependency versions when prebuilding (#23146)

# Why

In the past, we've had issues with bugfixes and minor bumps causing
issues in user projects, without user knowledge of these bumps.

# How

Instead of overwriting, the user is prompted with a warning that they
arent using the recommended versions. This can be resolved with `expo
install --fix` before prebuilding.

# Test Plan

- `$ yarn create expo ./test`
- Downgrade (patch or minor) any of these packages:
- `expo`, `expo-splash-screen`, `react`, or `react-native`
- `$ yarn expo prebuild`
- This command should warn you that you are not using the recommended
versions. It should NOT change these versions.

# 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 `npx expo prebuild` & EAS Build
(eg: updated a module plugin).

---------

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

show more ...

[cli] remove --dev-client prebuild side effect (#23121)

# Why

the `--dev-client` is deprecated in sdk 49

# How

remove the side effect of adding `--dev-client` when prebuild

# Test Plan

[cli] remove --dev-client prebuild side effect (#23121)

# Why

the `--dev-client` is deprecated in sdk 49

# How

remove the side effect of adding `--dev-client` when prebuild

# Test Plan

ci pass

show more ...