chore(e2e-tests): wait for the text to eventually match in bulk delete test

[lerouxb]

Just a test flake I spotted: https://parsley.mongodb.com/test/10gen_compass_main_test_packaged_app_macos_14_arm_test_packaged_app_3_patch_ec74f265c0353bb9ba557d157255ec52248dd1fa_688b6dee7fd6740007ab1d06_25_07_31_13_21_51/0/323543995f8d4eee48aa7fca1b2b7473?bookmarks=0,4&shareLine=0

This happens to be the canonical use case for waitUntil() https://webdriver.io/docs/api/browser/waitUntil/

[Copilot]

Pull Request Overview

This PR addresses test flakiness by replacing a direct assertion with a retry mechanism using waitUntil() to wait for toast text to eventually match the expected content.

• Replaces immediate text assertion with waitUntil() retry pattern for toast message verification
• Changes from throwing assertion to returning boolean for async waiting

Comments suppressed due to low confidence (1)

packages/compass-e2e-tests/tests/collection-bulk-delete.test.ts:112

• The waitUntil() pattern should include a timeout and meaningful error message for when the condition is not met within the expected timeframe. Consider adding a timeout parameter and descriptive error message.

      return toastText.includes('1 document has been deleted.');