fix(data-service): remove compass connectivity check via ping COMPASS-9455

[nbbeeken]

Description

We now use a driver version that does connection checkout/in verifying connectivity and auth in the connect method!! -1 RTT. huge!

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
• If this change could impact the load on the MongoDB cluster, please describe the expected and worst case impact
• 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

Removes the explicit post-connect ping round-trip in data-service so connections rely on the driver’s connect() verification, reducing one RTT during connection establishment.

Changes:

• Removed the runCommand(..., { ping: 1 }) connectivity check after creating a client.
• Updated the test suite by removing the ping/readPreference-specific assertion and associated type import cleanup.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 1 comment.

File	Description
packages/data-service/src/connect-mongo-client.ts	Drops the explicit ping command executed right after connectMongoClient() completes.
packages/data-service/src/connect-mongo-client.spec.ts	Removes a ping-specific test and cleans up now-unused MongoDB event typing.

[gribnoysup]

Not a bad suggestion to add a new test for this, otherwise lgtm

[nbbeeken]

Depends on: mongodb-js/devtools-shared#628

[nbbeeken]

chrome passed the same tests that failed of firefox here, and main is red right now too so I think they are flakes