fix(e2e-tests): wait for diagram nodes to be visible COMPASS-9627

[mabaasit]

Ticket: COMPASS-9627

Description

Checklist

• New tests and/or benchmarks are included
• Documentation is changed or added
• If this change updates the UI, screenshots/videos are added and a design review is requested
• I have signed the MongoDB Contributor License Agreement (https://www.mongodb.com/legal/contributor-agreement)

Motivation and Context

• Bugfix
• New feature
• Dependency update
• Misc

Open Questions

Dependents

Types of changes

• Backport Needed
• Patch (non-breaking change which fixes an issue)
• Minor (non-breaking change which adds functionality)
• Major (fix or feature that would cause existing functionality to change)

[Copilot]

Pull Request Overview

This PR fixes a drag-and-drop operation in the e2e tests for the data modeling tab by changing how the pointer moves to the target node position.

• Simplifies the node positioning logic by using the element reference directly instead of calculating absolute coordinates
• Removes manual coordinate calculations that may have been causing positioning inaccuracies

[Copilot]

The division operations nodeSize.width / 2 and nodeSize.height / 2 could result in fractional pixel values. Consider using Math.round() to ensure precise positioning, similar to the original implementation.

Suggested change

	.move({ origin: node, x: nodeSize.width / 2, y: nodeSize.height / 2 })
	.move({ origin: node, x: Math.round(nodeSize.width / 2), y: Math.round(nodeSize.height / 2) })

[paula-stacho]

Copilot has a point here, I think I've seen errors before I added the rounding

[paula-stacho]

The change makes sense to me, but I don't think this could've been causing the failure in
https://parsley.mongodb.com/test/10gen_compass_main_test_web_sandbox_test_web_sandbox_firefox_2_6881859323681900071339ec_25_07_24_01_00_03/0/92c0864f9996d1a502c0742d63abdb98?bookmarks=0,8&shareLine=0
This seems like the nodes were not displayed yet, leading to this check to fail:

    expect(nodes).to.have.lengthOf(2);

Were there other failures?

[paula-stacho]

Thank you! I honestly thought I'd already done this, must've removed it by accident