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 and captures the actual stdout, stderr, and exit code.
• Added tests/integration/cli-process-output.spec.ts asserting real output + exit codes for success and failure cases (asset-registry as the agentic-dev surface, plus version/unknown-command/required-option, and the GracefulError vs. regular-error exit-code 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
87.5% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud