[Spike] Analysis of current unit/feature/e2e tests in EO

As brought up during the 196 sprint retro -

We want to ensure that our code is being tested at the most appropriate level (can it be a unit test?)

We also want to break up our tests so that they are not overly complex and difficult to validate/troubleshoot.

Acceptance Criteria:

• Create a report on findings (tests that are functional/e2e but should be unit, e2e that should be functional, e2e tests are too large, etc)
• Create a follow up Logging(Explore) - Tech Debt card to use these findings to improve our current tests
• Evaluate code coverage for e2e tests (manual investigation) – will likely be an estimate

Non-goal:

• Evaluate code coverage for unit/functional tests – to be added to CI process

Dev notes:

• Rewrite Ginkgo tests with Go tests