Resiliency for components clicked in rapid succession

Overview

In one of our e2e tests, we quickly select a few components in the layout before making edits to the final one selected. This test began failing regularly until waits were added to confirm the form had fully loaded for a given component before clicking the next one.

Although the tests run much faster than a human can click, it might be possible to reproduce the problem IRL on a slower setup due to the complexity of the page || slow hardware || slow connection, especially if navigated via keyboard.

Note that any time these forms are visited for a second time in a given tab, Redux will first load the cached form (instantly loads but doesn't actually work!) and will quietly replace it with a fresh form as soon as the request completes. It may be a non-issue since waiting for the form's presence gets the test to work, but worth being aware of.

Proposed resolution

Probably to prevent the selection of a new component until the previously-selected component form has fully loaded

However, there's another option of addressing whatever is breaking when the fast selection occurs, as opposed to preventing that fast selection.

User interface changes