Improve terminal test output

[polishdataengineer]

What changed

• makes native testenix run compact by default, aggregating results per source file instead of printing one row per test
• adds -q, -v/-vv, --color, --no-color, --show-skips, and --durations
• preserves complete collection/failure diagnostics, full failing node IDs, the parseable final summary, JSON/JUnit contracts, and the transparent pytest bridge
• wraps unusually varied per-file status summaries without dropping the file path or status counts
• adds deterministic TTY/CI/color handling with no runtime dependency
• updates README, GitHub Pages sources, changelog, and LLM documentation

Why

The old native console output scaled linearly with the test count and produced a wall of text for large suites. The screenshot that prompted this change was direct pytest output, so the docs now clearly distinguish pytest's renderer from Testenix's native compact UI and recommend testenix pytest -q --tb=short tests for unchanged pytest suites.

User impact

A green native run now shows a short header, one aligned row per file, and one final summary. -q can reduce a green run to a single line, while -v retains the previous per-test format and -vv exposes worker/attempt/phase details. Failing node IDs remain complete and copyable.

Validation

• 333 passed
• Ruff check and format: clean
• mypy: clean
• pyright: 0 errors
• docs asset regeneration: identical on Python 3.11 and 3.14
• Sphinx 9.0.4 / Python 3.11 with -W: clean
• real migrated project: 118/118 native tests; compact, quiet, and pytest-bridge smoke tests passed
• 100,000 passing results from one file render in 5 lines and under 250 characters
• regression coverage for long parametrized failure IDs and multi-status rows in narrow terminals

The unrelated local .gitignore change is not included.