Cypress MVP

[Randy424]

At some point we will want to demo our Cypress solution to the console team and to the wider org.
To do so efficiently we will outline a "MVP" consisting of a few must-have requirements to get up and running:

1. Deliver an e2e testing suite that supports the most recent, stable, Cypress.
2. The testing suite should be geared towards maintainability, so we want to have strong confidence in our high-level structure for helper components, fixtures, and test suites. Components should be written and organized as to avoid duplication and enable ease of use for subsequent contributors. Documentation for code and organization should be included where necessary or useful.
3. To satisfy this epic, testing will cover a cross-section of the product (Credential & Cluster as our MVP?). In a subsequent epic, we will outline goals for migrating/refactoring the remainder of clc-ui-e2e.
4. Ensure the test suite is enabled for local testing and for production level testing in Prow. Prepare the necessary scaffolding for this suite to run automatically, (via maybe github actions) twice a day.
5. Develop a presentation that outlines how QE and Console will interact with the repo over the course of a train, and how it solves problems outlined in our Rework Doc