SP-1090: Assert on real process output and exit codes in integration tests

[A. Jashari (admirjashari)]

Description

Changes

• module-handler.ts: the shared command action wrapper now sets process.exitCode = 1 when a command throws, so errors surface as a non-zero exit code (previously thrown errors were only logged and the process still exited 0). GracefulError is preserved as exit 0.
• package.manager.ts: fixed a bare process.exit() (exited 0) on an error branch → process.exit(1).

Tests Added

• Added tests/utls/cli-runner.ts (runCli), which drives a command through the real Commander wiring — reusing the existing buildTestProgram helper — and captures the actual stdout, stderr, and exit code.
• Reworked the existing integration specs to run through runCli and assert on real captured output + exit codes instead of the injected logger transport:
  • configuration-management.spec.ts: validation errors now assert real output + non-zero exit code (replacing the in-memory winston transport checks).
  • asset-registry.spec.ts (the agentic-dev surface): each command asserts it exits 0 on success; error paths assert real output + exit code — service failure → exit 1, unknown command / missing required option → non-zero, and the GracefulError (exit 0) vs. regular-error (exit 1) contract.

Relevant links

• Jira: https://celonis.atlassian.net/browse/SP-1090

Checklist

• I have self-reviewed this PR
• I have tested the change and proved that it works in different scenarios
• I have updated docs if needed

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
100.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud