Fix autoCompact intermittent busy error

[danielfrankcom]

This change fixes a flaky failure in the autoCompact test suite, which can be triggered by asynchronous background processing.

autoCompact schedules a background task that winds down asynchronously. While it's winding down, any autoCompact call can be transiently rejected as busy.

Previously we attempted to work around this by ensuring an idle state at the start of each run, but it is not possible to reliably detect this without delving into engine internals. To work around this, each command execution has been modified to use the execute_admin_with_retry_command method, which allows the tests to tolerate this background task condition. The outcomes remain the same and will be eventually consistent, we just can't reliably get the engine into a clean starting state due to lack of engine-agnostic observability.

[documentdb-triage-tool]

🤖 Auto-triaged by documentdb-triage-tool.

Applied: compatibility test, bug
Project fields suggested: Component test-coverage · Priority P2 · Effort L · Status Needs Review
Confidence: 0.75 (mixed)

Reasoning

component from path globs (test-coverage, test-framework); effort from diff stats (52+38 LOC, 6 files); LLM: Fixes a flaky/intermittent test failure in the autoCompact suite by switching to retry-aware command execution, a small targeted fix within test code.

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.