[Spike] Investigate how to best enable automation testing with Cypress

[ArakTaiRoth]

Notes:

Right now, the only way to use Cypress for automation testing along with our components is to find the goa-input via a name property, then target the shadow dom, and then finally change the input box or click the button or something. We're interested in knowing if there's a better way to enable automation testing using our components and Cypress, so that people don't have to target the Shadow DOM.

Acceptance Criteria:

1. Find out if there's something we can change about how we build our components to enable Cypress automation testing without targeting the Shadow DOM.
2. Reach out to other teams that have implemented Cypress automation to see how they're testing our components
3. Documentation is created on the website for how to implement automated testing with our components

[Spark450]

Output of spike

[ArakTaiRoth]

Spike isn't done as there's a big unanswered question:

1. Currently the recommended way to target items in this spike won't trigger onChange functions in inputs or buttons. This is a big problem, as this is the main reason people would be testing our inputs and buttons. So this needs to be solved.