Add $ping tests

[PatersonProjects]

This PR adds the tests for the $ping operator, following the format of other diagnostic tests

Ref: Issue #43, #444

[documentdb-triage-tool]

🤖 Auto-triaged by documentdb-triage-tool.

Applied: compatibility test, enhancement
Project fields suggested: Component test-coverage · Priority P2 · Effort M · Status Needs Review
Confidence: 0.78 (mixed)

Reasoning

component from path globs (test-coverage); effort from diff stats (214+0 LOC, 5 files); LLM: Adds new test cases for the $ping operator following existing diagnostic test patterns, a focused test-coverage addition with minimal LOC impact.

If a label is wrong, remove it manually and ping @patty-chow so the rules can be tuned. The bot will not re-label items that already have component labels.

[fanyangv]

For consistency with buildInfo and listCommands tests, consider adding a test for ping on a nonexistent database (e.g., collection.database.client["nonexistent_db"]["coll"]).

[PatersonProjects]

In investigating this, I have learned that the basic test would be functionally identical to this case, since collection generates a new database reference which acts identical to the ["nonexistent_db"] name until any data is inserted. As such I have rather than adding this case removed the duplicate buildInfo case for consistency.