test(resource): regression coverage for JSON export CI progress

[cursor]

Description

Adds unit tests for _supports_live_progress and _ExportProgressReporter so installation/directory JSON export keeps emitting percentage milestones through the logger when CI or GITHUB_ACTIONS is set, even if stderr appears as a TTY (matching the fix in fix(json-export): log progress when automated).

Type of Change

• ✅ Test addition or update

Package(s) Affected

• PyKotor (core library)

Changes Made

• New file Libraries/PyKotor/tests/resource/test_resource_json_ci_progress.py covering:
  • CI=true disables live \r progress even for TTY-like streams
  • GITHUB_ACTIONS=1 does the same when CI is unset
  • CI=false does not force the logger path for a TTY stream
  • With CI enabled, _ExportProgressReporter logs percent lines and does not write carriage-return progress to the stream

Risky behavior now covered

• Silent loss of export progress in CI log aggregators if someone removes the CI / GITHUB_ACTIONS guard and relies only on isatty().

Test files added/updated

• Added: Libraries/PyKotor/tests/resource/test_resource_json_ci_progress.py

Why this reduces regression risk

Large installation JSON exports are long-running; operators rely on logs. The production change intentionally routes progress through logger.info in automation. These tests pin that contract without depending on a real TTY or RobustLogger singleton behavior (subclassing RobustLogger in tests is unsafe because of its metaclass).

Testing

cd Libraries/PyKotor && .venv/bin/python -m pytest --import-mode=importlib -m "not gui and not slow" tests/resource/test_resource_json_ci_progress.py -v
# 4 passed

• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes

Related Issues

Related to automated regression coverage for merged resource_json export progress behavior.