Build: Add e2e-tests-dev task

[yannbf]

What I did

We have been running e2e tests against built Storybooks, but not against Storybooks in dev mode.
This PR solves that!

How to test

Run a e2e-tests-dev for template, e.g. yarn task --task e2e-tests-dev --start-from auto --template react-vite/default-ts

Checklist

• Make sure your changes are tested (stories and/or unit, integration, or end-to-end tests)
• Make sure to add/update documentation regarding your changes
• If you are deprecating/removing a feature, make sure to update
  MIGRATION.MD

Maintainers

• If this PR should be tested against many or all sandboxes,
  make sure to add the ci:merged or ci:daily GH label to it.
• Make sure this PR contains one of the labels below.

["cleanup", "BREAKING CHANGE", "feature request", "bug", "documentation", "maintenance", "dependencies", "other"]

[tmeasday]

Can we factor things so we share the code between the two files?

We could have them read the same lib.

We could also consider a more complicated system where we can run any of the final tasks against either dev or build (arguably we could also run the test-runner task against dev also?) and have a flag that chooses between them, or a e2e-tests-dev task that depends on dev and e2e-tests somehow? Probably not the right time to think about that!

[tmeasday]

Also, let's make a ticket where we delete smoke testing from the repo if we all agree we don't need it any more.

[yannbf]

Can we factor things so we share the code between the two files?

We could have them read the same lib.

We could also consider a more complicated system where we can run any of the final tasks against either dev or build (arguably we could also run the test-runner task against dev also?) and have a flag that chooses between them, or a e2e-tests-dev task that depends on dev and e2e-tests somehow? Probably not the right time to think about that!

Would you like to take a stab at it @tmeasday? Feel free to change this PR or make a telescoping one!

[shilman]

@tmeasday @yannbf Can we limit our dev coverage to 1 webpack-based project and 1 vite-based project and perhaps 1-2 others at most? If not, we're nearly doubling our CI costs, right? If we adopt nx affected and are able to dramatically reduce costs that way, we can look at testing dev more aggressively. WDYT?

[yannbf]

@tmeasday @shilman I worked on it based on your feedback. Please check!

[tmeasday]

LGTM. We should talk about a better way to disable a given task at a given cadence but this way is good for now!

[yannbf]

I'd love some help to understand why these tests fail in CI:

[tmeasday]

@yannbf if you are stuck I can have a go at figuring it out tomorrow perhaps?

[yannbf]

@yannbf if you are stuck I can have a go at figuring it out tomorrow perhaps?

Thank you!