chore(CI): CI telemetry checking

[Josh-Walker-GM]

Problem
We have no way of checking at the CI level that PRs are not breaking the telemetry setup.

Changes

1. Adds a CI check which executes both the CRWA and the CLI scripts and listens for telemetry which is redirected to localhost instead of telemetry.redwoodjs.com.
2. Adds an env var REDWOOD_REDIRECT_TELEMETRY which overrides the default telemetry endpoint of telemetry.redwoodjs.com when set. Needed because it is too complex to try and run a https listener on port 80 within the CI.

Outstanding

1. Need to let the telemetry fix go in first.
2. Decide if we should add the bundler flag? I think so. I added it in.

Ping
@thedavidprice

[replay-io]

16 replays were recorded for 91269d5.

0 Failed

16 Passed

requireAuth graphql checks

locator.waitFor: Target closed
=========================== logs ===========================
waiting for locator('.rw-form-error-title').locator('text=You don\'t have permission to do that') to be visible
============================================================

• useAuth hook, auth redirects checks
• Check that tags are rendering the correct dynamic data
• Check that a specific blog post is prerendered
• Check that about is prerendered
• Check that homepage is prerendered
• Check that you can navigate from home page to specific blog post
• Waterfall prerendering (nested cells)
• RBAC: Admin user should be able to delete contacts
• RBAC: Should not be able to delete contact as non-admin user
• Smoke test with dev server
• Smoke test with rw serve
• Loads Cell mocks when Cell is nested in another story
• Loads Cell Stories
• Loads MDX Stories
• Mocks current user, and updates UI while dev server is running

View test run on Replay ↗︎

[jtoar]

Looks good @Josh-Walker-GM! Left a few comments, but not much left to do otherwise. Also I'm going to push up a commit that just runs yarn lint on this new file. (The actual command is slightly more complicated than that since eslint ignores dot directories.)

[thedavidprice]

Nice! 🚀

[Josh-Walker-GM]

Okay @jtoar I think I've addressed your concerns about the hard coded host/port. I've also added in the corresponding check for telemetry from the CLI. Hope that running yarn install within the check won't introduce any issues?

Can you apply some of your linting secret sauce again please?

[jtoar]

yarn install won't matter, let's merge it