[lint] Upgrade to Prettier v3, typescript-eslint to v6 (#23544)

Why
---
Prettier 3 is out. Add support for it with this linter config.

**Note for reviewer:** the first commit is the one with th

[lint] Upgrade to Prettier v3, typescript-eslint to v6 (#23544)

Why
---
Prettier 3 is out. Add support for it with this linter config.

**Note for reviewer:** the first commit is the one with the actual
changes. The rest of this PR are changes to get the linter passing
(mostly autofix).

How
---
Update eslint-config-prettier and eslint-plugin-prettier. To address
deprecation warnings, also update typescript-eslint/parser and
typescript-eslint/eslint-plugin.
Because of an update to typescript-eslint/parser, we need to suppress
deprecation warnings (documented in a comment).

Regenerated test snapshots. Due to the upgraded dependencies, typecasts
and optional chaining are now auto-fixable by lint. This converts
warnings into autofixes.

Test Plan
---
`yarn test` in the linter config. Run `expotools check --all --fix-lint
--no-build --no-test --no-uniformity-check` to try this config on the
whole repo.

---------

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

show more ...

[templates][config-plugins][dev-server] aligned hermesEnabled property (#21067)

# Why

react-native 0.71 introduces `hermesEnabled` gradle property which is conflict with the original `expo.jsEngi

[templates][config-plugins][dev-server] aligned hermesEnabled property (#21067)

# Why

react-native 0.71 introduces `hermesEnabled` gradle property which is conflict with the original `expo.jsEngine` in gradle.properties. this pr tries to align the `hermesEnabled` as upstream.
close ENG-7228

# How

deprecate `expo.jsEngine` in **gradle.properties** and use `hermesEnabled` instead.

# Test Plan

ci passed

show more ...

Switch default JS engine to Hermes (#21001)

# Why

Closes ENG-7163

# How

Update `@expo/config-plugins`, `@expo/dev-server`, all templates and
`packages/expo-manifest` to use Hermes as the d

Switch default JS engine to Hermes (#21001)

# Why

Closes ENG-7163

# How

Update `@expo/config-plugins`, `@expo/dev-server`, all templates and
`packages/expo-manifest` to use Hermes as the default JS engine

Follow ups
- [x] Update `Using Hermes Engine` guide
(https://github.com/expo/expo/pull/21047)
- [x] Update xdl schema (https://github.com/expo/universe/pull/11355)

# Test Plan


```bash
# create a new project
npx create-expo-app hermes-app
cd hermes-app
# run local expo cli
nexpo prebuild --no-install
```

# 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)
- [x] This diff will work correctly for `expo prebuild` & EAS Build (eg:
updated a module plugin).

---------

Co-authored-by: Douglas Lowder <[email protected]>

show more ...

chore: migrate config, config-plugins, config-types, prebuild-config (#17958)