[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 ...

[test-suite][barcode] Fix tests (#19616)

# Why

Fixes:
```
- Barcode scanner
- tests failed:
- scans a QR code from asset
- scans a Data Matrix code from asset
```

# H

[test-suite][barcode] Fix tests (#19616)

# Why

Fixes:
```
- Barcode scanner
- tests failed:
- scans a QR code from asset
- scans a Data Matrix code from asset
```

# How

It turns out that the results are one pixel higher than expected. In the case of calculating the bounding box of the image, it's not a huge difference. Probably something was changed in the underlying library. So changing the size inaccuracy should be fine in that case. Especially, in other tests, we're using much bigger inaccuracy.

# Test Plan

- change the size inaccuracy.

show more ...

[test-suite] lint files, add lint check to CI (#15772)

[test-suite] Use permission requesters from modules instead of expo-permissions (#12199)

[expo-barcod-scanner] Return bounding box (#8865)

# Why

Fixes https://github.com/expo/expo/issues/8754 and https://github.com/expo/expo/issues/2700.

# How

- Readd the bounding box informati

[expo-barcod-scanner] Return bounding box (#8865)

# Why

Fixes https://github.com/expo/expo/issues/8754 and https://github.com/expo/expo/issues/2700.

# How

- Readd the bounding box information on Android (previously added by https://github.com/expo/expo/pull/2904).
- Add the same functionality to iOS.
- Update NCL and test-suite

Unfortunately, currently, we don't always return this information on iOS. For some barcode types, there is a problem with converting point coordinates from one space to another.

# Test Plan

Tested using updated NCL and test-suite:
- iOS ✅
- Android ✅

show more ...

[ncl][test-suite] Change imports to SDK 33 syntax with the codemod (#4219)

* [ncl][test-suite] Change imports to SDK 33 syntax with the codemod

* [ncl][test-suite] Add new imported packages to de

[ncl][test-suite] Change imports to SDK 33 syntax with the codemod (#4219)

* [ncl][test-suite] Change imports to SDK 33 syntax with the codemod

* [ncl][test-suite] Add new imported packages to dependencies

show more ...

Move test-suite into the Expo repo under apps

This moves test-suite into the Expo repo, setting things up so that CI can verify changes to modules using test-suite.

Tested by loading and running te

Move test-suite into the Expo repo under apps

This moves test-suite into the Expo repo, setting things up so that CI can verify changes to modules using test-suite.

Tested by loading and running test-suite with `expu start` for now. Also will check that our CI passes since there are some dependencies on test-suite (e.g. publishing it). Before merging, the shipit bot needs to be redeployed as well and may need some manual repo editing inside its container.

fbshipit-source-id: 144e1bd

show more ...