chore(cli): test watchman for e2e cli tests

[byCedric]

Why

See if we get any performance boost out of the cli e2e tests with watchman, specifically, the export tests.

How

• Disabled cli e2e sharding
• Installed watchman for cli e2e tests

Test Plan

See GitHub Actions.

Checklist

• Documentation is up to date to reflect these changes (eg: https://docs.expo.dev and README.md).
• Conforms with the Documentation Writing Style Guide
• This diff will work correctly for npx expo prebuild & EAS Build (eg: updated a module plugin).

[expo-bot]

Hi there! 👋 I'm a bot whose goal is to ensure your contributions meet our guidelines.

I've found some issues in your pull request that should be addressed (click on them for more details) 👇

⚠️ Suggestion: Missing changelog entries

Your changes should be noted in the changelog. Read Updating Changelogs guide and consider adding an appropriate entry to the following changelogs:

• packages/@expo/cli/CHANGELOG.md

---

Generated by ExpoBot 🤖 against 33065af

[byCedric]

lmao @EvanBacon. This is not feasable until we've stopped binding the server for static exports. 8082 might be taken during start-up when not running in the band but still passing the getFreePortAsync check.

Overal time to install watchman is 1m30s/2m. Which isn't fast (enough) for now, will only be faster if we add more e2e tests.