e2e: double ForeverTestTimeout wait tracker

[gman0]

This ticket is to track places in our codebase where we use 2*ForeverTestTimeout with Eventually().

Let's see if this actually fixes the flakes (which would suggest infra issues) or not, and proper fix needs to be done.

We should try to remove these 2*ForeverTestTimeout when possible, and using these fixes as the last resort.

[gman0]

• attempt to fix flake in TestCachedResources #3814
• fix flake in TestTerminatingWorkspacesVirtualWorkspaceWatch #3801

[neolit123]

with a lot happening in parallel and infra under heavy load the only option might be increased timeouts.
removing some of the t.Parallel() from heavy tests, gets my +1 too.

[neolit123]

$ grep "\*wait\.ForeverTestTimeout" * -rnI
test/e2e/authorizer/authorizer_test.go:118:     }, 2*wait.ForeverTestTimeout, 100*time.Millisecond)

$ grep "wait\.ForeverTestTimeout\*" * -rnI
test/e2e/reconciler/apiexportendpointslice/apiexportendpointslice_test.go:333:          }, wait.ForeverTestTimeout*50, time.Millisecond*500)
test/e2e/reconciler/apiexportendpointslice/apiexportendpointslice_test.go:381:          }, wait.ForeverTestTimeout*50, time.Millisecond*500)
test/e2e/reconciler/apiexportendpointslice/apiexportendpointslice_test.go:406:          }, wait.ForeverTestTimeout*50, time.Millisecond*500)
test/e2e/virtualresources/cachedresources/vr_cachedresources_test.go:367:       }, wait.ForeverTestTimeout*2, time.Millisecond*500, "waiting for two sheriffs")
test/e2e/virtual/terminatingworkspaces/virtualworkspace_test.go:623:                    }, wait.ForeverTestTimeout*2, 100*time.Millisecond)