fix(deploy: exit non-zero if uncommitted changes are present

[sakethsomaraju]

Description

Describe the purpose of this pull request.

Customers using GitLab or other CI/CD platforms rely on command exit codes to programmatically determine whether an astro deploy invocation succeeded or failed.

🎟 Issue(s)

Related #1721

🧪 Functional Testing

List the functional testing steps to confirm this feature or fix.
Run astro deploy with uncommitted git changes --> command fails with error and exits non-zero.

Run astro deploy -f with uncommitted changes --> deploy proceeds successfully.

Run astro deploy with a clean git state --> deploy succeeds as before.

📸 Screenshots

📋 Checklist

• Rebased from the main (or release if patching) branch (before testing)
• Ran make test before taking out of draft
• Ran make lint before taking out of draft
• Added/updated applicable tests
• Tested against Astro-API (if necessary).
• Tested against Houston-API and Astronomer (if necessary).
• Communicated to/tagged owners of respective clients potentially impacted by these changes.
• Updated any related documentation

[github-actions]

This PR is stale because it has been open for 60 days with no activity.

[coveralls-official]

Coverage Report for CI Build 29357736272

Coverage increased (+0.001%) to 43.89%

Details

• Coverage increased (+0.001%) from the base build.
• Patch coverage: 1 uncovered change across 1 file (0 of 1 lines covered, 0.0%).
• No coverage regressions found.

Uncovered Changes

File	Changed	Covered	%
cmd/cloud/deploy.go	1	0	0.0%

Coverage Regressions

No coverage regressions found.

---

Coverage Stats

Relevant Lines:	59016
Covered Lines:	25902
Line Coverage:	43.89%
Coverage Strength:	8.55 hits per line

---

💛 - Coveralls