Fix CLI error handling and exit codes for failed commands

[rjgoyln]

Summary

This PR fixes an issue in CLI error handling where certain failures (e.g. network or server errors) were only printed but did not cause the process to exit with a non-zero status code.
As a result, CI systems could incorrectly interpret failed executions as successful runs.
This change ensures proper error propagation and correct exit code behavior for CLI failures.

Changes

• Ensure all CLI execution errors properly trigger failure exit codes
• Ensure sys.exit(1) is triggered on all failure cases

---

Was generative AI tooling used to co-author this PR?

• Yes (please specify the tool below)

---

• Read the Pull Request Guidelines for more information. Note: commit author/co-author name and email in commits become permanently public when merged.
• For fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
• When adding dependency, check compliance with the ASF 3rd Party License Policy.
• For significant user-facing changes create newsfragment: {pr_number}.significant.rst, in airflow-core/newsfragments. You can add this file in a follow-up commit after the PR is created so you know the PR number.

[bugraoz93]

Thanks! I think this needs revision

[bugraoz93]

We are specifically not exit anything api side of the code. Id you think this isn't handled, I would suggest add into cli_config.py safe_call where we directly handle exceptions at the most closest to user