[cli] Improve Tests

[danstepanov]

Currently

• Tests currently test the local files rather than the the build folder which means that the tests can pass while running npx create-expo-stack@latest can be broken.
• Running tests is slow and/or trips up with bun
• Tests do not have full coverage
• Tests don't even pass locally

What this is

We need to be able to ensure that every single iteration of configurations and flags works as expected, at any point in time but particularly upon any change made to the cli.

The way to confirm that each iteration works is to ensure that:

• Project set up succeeds, which is to say that
  • The appropriate cli json object is created
  • The appropriate command is generated to rerun the command, if desired by the user
  • Project initialization succeeds
  • Initializing git succeeds (flag)
  • Base assets are copied
  • Installation of dependencies succeeds with the specified package manager (flag)
  • Code formatting completes
• All of the elements on each screen are present, laid out properly, with the proper styles applied (android & ios)
• Navigating throughout the application should function as expected such that clicking on a button will lead you to the appropriate page and clicking some other button will return you to the previous page (android & ios)

Conditions

• Tests should run on the build folder rather than the the local folder to prevent tests passing locally while breaking in production (eg npx create-expo-stack@latest)
• If they are to be run locally, they can't take too long (more than 2 min is too much)
• Tests should not run on commit
• A PR pertaining to the cli should not be able to be merged without tests passing
• Going through the CLI interactively, all iterations work
• Going through non-interactive mode, all iterations work

What this is not

• Tests for the landing page
• Tests for the docs

[danstepanov]

https://maestro.mobile.dev/platform-support/react-native

https://maestro.mobile.dev/getting-started/running-flows-on-ci#alternatives