Only auto-wait after visit for allowlisted suites
What does this MR do and why?
wait_for_requests after page visits is unreliable. Rather than removing it
everywhere at once (see !234933 (merged)), this gates the
auto-wait behind an allowlist of the spec suites that currently fail without
it. Every other feature spec gets a plain pass-through visit, so suites can
be migrated incrementally to assert on UI changes instead.
The allowlist was derived from the failing rspec system / rspec-ee system
jobs in pipeline
2562075595
(the test run of !234933 (merged)). Non-feature specs were excluded.
Only visit is gated; the click_button auto-wait is unchanged.
Related: #525094 (closed)
MR acceptance checklist
Evaluate this MR against the MR acceptance checklist.