[CagriYonca]

Why

When pytest failed in CI, the test job stopped right away, before coverage, pip freeze output and test metadata were saved to the workspace. Downstream jobs then had no artifacts on failed runs, so rupy-currency-reporter never got updated dependency or test-status data.

How

• run-tests-with-coverage-report now saves the pytest exit code and lets the remaining steps run instead of stopping the job.
• A new fail-if-tests-failed command runs last in every test job (when: always). It fails the job only after all artifacts and workspace files are saved, and it prints the pytest short summary.
• Failed test module names are parsed from the pytest output (e.g. tests/frameworks/test_fastapi.py → fastapi) and saved per job as pytest_failed_<label>.txt.
• capture-installed-versions now runs with when: always, and the autowrapt job also saves its pip freeze output.
• update-currency-versions combines the failed modules from all jobs into a package-level test-status.json ({"<package>": "fail"}; packages that aren't listed passed). The file is published next to installed_*.txt.
• final_job and update-currency-versions now use requires: <job>: terminal, so they run whether the test jobs pass or fail.

Verification

• Checked that the exit codes, failed-module lists and pip freeze files are saved on both passing and failing runs.
• Checked that the generated test-status.json works with rupy-currency-reporter (instana/rupy-currency-reporter#9).

[GSVarsha]

Looks good to me.