Figure out how to support/enable E2E tests for extensions

[nwmac]

Figure out how to support/enable E2E tests for extensions (formerly plugins)

[gaktive]

Might require a 2nd ticket so that we periodically check other projects (Kubewarden, Elemental) to see that extensions don't break.

[aalves08]

@gaktive what's the scope/goals of this issue? 🙏

[gaktive]

Let's check in with @nwmac when he's back but the key thinking here is how to regularly test the UI so that extensions don't break over time.

[aalves08]

Ok. sounds good @gaktive . We have e2e tests for Elemental and Kubewarden already in place, so the goal is to figure out how to run them from time to time in our Dashboard test suite. 🙏

[aalves08]

After some investigation on how to run the e2e tests that are already coded for Kubewarden and Elemental from a Dashboard workflow, it's very difficult to achieve because one of those e2e it's written for Playwright (kubewarden) and the other has a very specific environment that it runs on (elemental - https://github.com/rancher/elemental/tree/main/tests/cypress/latest).

Improving the test-plugins-build script to test extension build seems like an "easy" win in light to the work to run those e2e (if it's even possible to do so). With this we are increasing our test coverage on extension, even if indirectly.

FYI @nwmac @gaktive