fix: correct tests to be handled by faster ci runner

[wdoconnell]

Part of internal AUX team issue.

Best reviewed with ?w=1 for whitespace changes

This PR resolves several issues with UI e2e tests that cause the tests to fail when running on a different CI runner. Primary issue is that existing runners generated some built-in delay was effectively adding a .wait() or should() where not present in the code. On the faster runner this is no longer the case.

1. Using cy.waits to handle cases where a click did not wait for a corresponding DOM change. Once this is tested with the new runner, I would prefer to convert waits to asserting on the presence of specific DOM elements if time allows.
2. Using .first() to handle cases where later renders generated more than one DOM element matching on the selector when we are only looking for the first one.
3. Cleaned up cases where cy.reload() caused a page reload without setting feature flags.

Checklist

Authors and Reviewer(s), please verify the following:

• A PR description, regardless of the triviality of this change, that communicates the value of this PR
• Well-formatted conventional commit messages that provide context into the change
• Documentation updated or issue created (provide link to issue/PR)
• Signed CLA (if not already signed)
• Feature flagged, if applicable

[wdoconnell]

Failed status checks were network errors unable to reach a pod.