[CI] Improve (and complete) new CLI check

[thedavidprice]

continues work from:

• Adds a CI Check to run CLI against Windows and Ubuntu; adds build:test-project as reusable fixture #4495

cc @dac09 @jtoar

What's the point:

• make test-project use more efficient
• use test-project for CI
• use test-project as a fixture for unit tests
• remove CLI checks from E2E CI Workflow
• add missing CLI checks to CI
• replace telemetry-benchmarks workflow with this one

CLI checks

• Need to run yarn rw dev and yarn rw serve
  • Add smoke test for rw dev and rw serve commands #4259
  • E2E Smoke test #4497
• How to handle rw setup command: tailwindcss, chakra-ui, auth, deploy, etc: they all fail even if using yarn dev <command> --cwd ... due to setup trying to install yarn workspace web add ... during the process
• enable rw check: currently has a legitimate error (there's a createContact mutation, but not service)
• enable rw type-check: throwing "gql missing" error, which is not reproducible locally.

Codemods for build:test-project

• resolve yarn rw lint errors in built test-project
• resolve missing createContact in Service
• add prerender to NotFoundPage and HomePage

build:test-project option

• --re-build-fixture: option to build new project at ./__fixtures__/test-project
  • typescript
  • latest published version of Redwood Packages
  • remove yarn.lock
  • probably need to build in /tmp outside directory and then copy back ('cause Yarn 1)
• --copy-from-fixture: default=true, when running build:test-project use codebase at __fixtures/test-project to copy into target directory instead of creating codebase from scratch
  • E2E Smoke test #4497
• determine a process about when to rebuild __fixtures__/test-project: breaking change, adding feature/code to test, new codemod, etc.?

publishing Redwood packages

• should we rebuild __fixtures__/test-project each time we publish?
  • probably "no"
• ==> or just update package versions (along with script "update-package-versions)?
  • add __fixtures__/test-project packages to "update-package-versions"

[thedavidprice]

Calling this one good as of #4563

Moving next steps over to #4486