Add skip_localhost mark, skip shutdown on local

[PatersonProjects]

This PR changes the contest and ini to add the needed mark to prevent the shutdown command from running on localhost devices (determined by checking the uri connected to mongo), helping prevent the destructive shutdown failing local test runs.

[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.75 (mixed)

Reasoning

component from path globs (test-coverage); effort from diff stats (20+1 LOC, 3 files); LLM: Adds a pytest mark to skip destructive shutdown commands on localhost, improving local developer experience in the test framework (conftest/ini changes).

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.

[eerxuan]

Can you remind me what's the behavior on local host what is behavior on remove host?
CI also skips it:

skip_localhost:
  Total:   1
  Passed:  0 (0.0%)
  Failed:  0
  Skipped: 1

Then when will we run this?

[PatersonProjects]

Sorry, this came about as a misunderstanding on my part of how Docker was being run in CI, thank you for catching this. The goal is that it is skipped on local runs and passes on remote runs, as if the test ever fails it kills the connection and ruins the whole test run. I have made this earlier change to be a fallback and introduced a new check that allows CI to run the test.

[ramgokul-14]

• [Required] Fail-open on a destructive gate. In conftest.py, except Exception: nodes = [] makes an unparseable URI resolve to not localhost → the destructive shutdown runs. A safety guard must fail safe: on parse failure, treat as localhost and skip. This is the most important fix.

• [Required] Missing docs update (§9 of docs/REVIEW.md). The guideline explicitly requires TEST_FORMAT.md to be updated when a PR introduces a new mark. skip_localhost is a new mark; no doc change is included.

• [Suggestion] Reuse the existing requires(...)/preconditions gate instead of a bespoke loop. The new code even comments that it "mirrors the requires(...) gate" — modeling this as a capability (e.g. requires(remote_target=True)) would deselect rather than skip, reuse per-target resolution and auto-registration, and avoid a parallel mechanism. §6 of the guide leans toward requires(...) for environment-gated tests.

• [Suggestion] Host-matching edge cases: {localhost, 127.0.0.1, ::1} misses 0.0.0.0 (common in Docker/dev) and hostnames that resolve to loopback. Add 0.0.0.0 at minimum.

• pytest.ini marker description could state the purpose (safety guard for destructive commands), not just the mechanic.

• Consider co-locating the parse_uri import with its usage or commenting why it's module-level.

[PatersonProjects]

• [Required] Fail-open on a destructive gate. In conftest.py, except Exception: nodes = [] makes an unparseable URI resolve to not localhost → the destructive shutdown runs. A safety guard must fail safe: on parse failure, treat as localhost and skip. This is the most important fix.
• [Required] Missing docs update (§9 of docs/REVIEW.md). The guideline explicitly requires TEST_FORMAT.md to be updated when a PR introduces a new mark. skip_localhost is a new mark; no doc change is included.
• [Suggestion] Reuse the existing requires(...)/preconditions gate instead of a bespoke loop. The new code even comments that it "mirrors the requires(...) gate" — modeling this as a capability (e.g. requires(remote_target=True)) would deselect rather than skip, reuse per-target resolution and auto-registration, and avoid a parallel mechanism. §6 of the guide leans toward requires(...) for environment-gated tests.
• [Suggestion] Host-matching edge cases: {localhost, 127.0.0.1, ::1} misses 0.0.0.0 (common in Docker/dev) and hostnames that resolve to loopback. Add 0.0.0.0 at minimum.
• pytest.ini marker description could state the purpose (safety guard for destructive commands), not just the mechanic.
• Consider co-locating the parse_uri import with its usage or commenting why it's module-level.

Updated to use the new preconditions, which also helps fix the open gate. Updated documentation and descriptions

[ramgokul-14]

Were subtract related files unintentionally added?