BDMS-167: Cypress with Cucumber Preprocessor - Features with Steps Example

[chasetmartin]

Why

This PR addresses the following problem / context:

• We need to make a decision as a team about whether we want Cypress tests in the UI to run with Cucumber processing against Gherkin feature files.

How

Implementation summary - the following was changed / added / removed:

• Adds https://github.com/badeball/cypress-cucumber-preprocessor
• Follows quickstart docs for cypress config setup
• Points the preprocessor to the cypress/e2e/ocotillo/steps folder to find the step test files
• Adds one example feature file and steps file for identifying items on the well-show page (well details)

Notes

Any special considerations, workarounds, or follow-up work to note?

[chasetmartin]

@jirhiker @TylerAdamMartinez @kbighorse @jasnakai @jacob-a-brown @ksmuczynski This draft PR is somewhat related to this discussion: https://github.com/orgs/DataIntegrationGroup/discussions/26

• Do we want frontend testing to use cucumber processing against Gherkin syntax so we can utilize feature files like the OcotilloAPI?
• And if so, should UI presentation/interaction logic feature files live in the OcotilloUI repo? The separate BDD repo? Or in OcotilloAPI? The later two options would require the OcotilloUI repo to use a script or git submodule to pull feature files from the external repo.