chore(e2e-tests): wait for documents to appear on view swap before value check COMPASS-10205

[Anemy]

COMPASS-10205

This should hopefully fix the flake in this test, my hunch is that we were checking for the value of the document before the view had swapped which caused occasional failures.

Here are my investigation notes:
One test failed on “expected undefined to equal '"10101010"'” on line 778

compass/packages/compass-e2e-tests/tests/in-use-encryption.test.ts

Line 778 in 378e982

expect(modifiedResult.phoneNumber).to.be.equal('"10101010"');

The other test failed on “expected [ …(4) ] to have a length of +0 but got 4” line 777

compass/packages/compass-e2e-tests/helpers/commands/read-first-document-content.ts

Line 20 in 378e982

expect(fieldValues).to.have.lengthOf(fieldNames.length);

So the field values exist, but not field names yet. I am thinking it's a the race between the two requests for the field names and field values even. (names happens first and it’s length 0).

So the runFindOperation isn’t checking for the expected status in the respective view when the view is swapped (here it's JSON -> list view).

From the screenshots, which happen after the check, it looks like it’s the right content being shown.

[Copilot]

Pull request overview

This PR fixes a flaky end-to-end test by adding a wait condition to ensure documents are fully rendered after a view swap from JSON to list view.

• Adds explicit wait for document list entry to be displayed before reading document content
• Prevents race condition between view swap completion and value verification