test(cli): cover JSON export live-progress CI env gates

[cursor]

Description

Adds unit tests for _supports_live_progress in resource_json.py, which gates whether installation JSON export uses live \r stderr updates versus logger.info milestones. Recent production changes treat CI / GITHUB_ACTIONS as forcing the logger path so CI and log aggregators reliably capture percentage progress.

Type of Change

• Test addition or update

Package(s) Affected

• PyKotor (core library)

Risky behavior now covered

• CI / GitHub Actions env: When stderr is still a TTY (common in some runners), live progress would skip structured logs; the code now disables live updates when CI or GITHUB_ACTIONS is truthy (true / 1 / yes, case-insensitive). Tests assert False is returned for a fake TTY stream under those env vars, and True when they are unset and the stream reports a TTY.
• Non-TTY streams: Asserts False when isatty() is false and CI env is clear (unchanged path, guards regressions).

Test files added/updated

• Libraries/PyKotor/tests/cli/test_json_commands.py — three tests: CI vs TTY interaction, whitespace/case on CI, non-TTY stream.

Why this reduces regression risk

This logic is easy to break with a small refactor (e.g. reordering isatty vs env checks) and has direct impact on observability and the existing caplog-based CLI test for percentage milestones. Deterministic tests use monkeypatch only; no network or filesystem dependencies.

Testing

Ran (from Libraries/PyKotor with dev venv):

QT_QPA_PLATFORM=offscreen .venv/bin/python -m pytest --import-mode=importlib -m "not gui and not slow" tests/cli/test_json_commands.py -k "supports_live_progress" -v

Result: 3 passed.

Test Results

3 passed, 28 deselected