Revert flakey test changes and increase MUO SpecTimeout to 3 minutes

[Copilot]

The previous attempt to fix flakey tests in test/e2e/operator.go replaced GetK8sObjectWithRetry with Eventually-based helpers and removed the SpecTimeout from the MUO deployment spec, risking unbounded hangs in the test suite.

Changes

• Reverted test/e2e/operator.go to its original state, restoring GetK8sObjectWithRetry usage and removing the waitForMUODeploymentReady/waitForGatekeeperDeploymentReady helpers
• Increased SpecTimeout on the MUO "must be restored if deleted" spec from 2*time.Minute → 3*time.Minute to reduce flakiness while preserving the suite-level hang protection

// Before
}, SpecTimeout(2*time.Minute))

// After
}, SpecTimeout(3*time.Minute))

---

📍 Connect Copilot coding agent with Jira, Azure Boards or Linear to delegate work to Copilot in one click without leaving your project management tool.

[openshift-ci]

Hi @copilot. Thanks for your PR.

I'm waiting for a Azure member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work.

Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.