Abort the CLI immediately on SIGTERM/SIGINT (CI cancellation)

[dfrankland]

Problem

GitHub Actions (and most CI) cancel a job by signaling the process tree. The CLI installed no signal handlers and blocked on its work, so a cancellation couldn't fully complete until slow operations (e.g. the API retry loop or telemetry upload) finished on their own — customers reported jobs that wouldn't cancel until the slow upload completed.

Change

• main now races the command against termination signals via tokio::select!. On SIGTERM/SIGINT (Unix) or Ctrl-C (Windows), the in-flight work future is dropped — cancelling outstanding requests and the retry loop immediately — and the process exits with the conventional 128 + signal code.
• If handler installation fails, falls back to the OS default disposition, so behavior is no worse than before.
• Signal handling lives in its own module (cli/src/shutdown.rs) to keep main.rs focused; exit codes are named constants (EXIT_CODE_SIGINT = 130, EXIT_CODE_SIGTERM = 143) with a comment noting these come from the POSIX 128 + signal convention, which the exitcode/sysexits crate doesn't define.
• Adds the signal feature to the cli crate's tokio dependency (pulls signal-hook-registry into Cargo.lock).

Notes

This is the complementary fix to #1131 (retry deadline): the deadline bounds total retry time but is checked between attempts; this PR provides true immediate mid-request abort when CI actually cancels. The two are independent and can merge in any order.

Testing

• cargo build -p trunk-analytics-cli clean on this branch standalone (off main, without the Add TRUNK_API_CLIENT_RETRY_DEADLINE_SECS to bound API retry time #1131 changes).

🤖 Generated with Claude Code

[trunk-io]

😎 Merged directly without going through the merge queue, as the queue was empty and the PR was up to date with the target branch - details.

[codecov-commenter]

Codecov Report

❌ Patch coverage is 57.14286% with 12 lines in your changes missing coverage. Please review.
✅ Project coverage is 82.68%. Comparing base (83033bf) to head (61acc24).

Files with missing lines	Patch %	Lines
cli/src/shutdown.rs	47.05%	9 Missing ⚠️
cli/src/main.rs	72.72%	3 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #1132      +/-   ##
==========================================
+ Coverage   82.48%   82.68%   +0.20%     
==========================================
  Files          69       70       +1     
  Lines       15482    15505      +23     
==========================================
+ Hits        12771    12821      +50     
+ Misses       2711     2684      -27     

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[trunk-staging-io]

     

Failed Test	Failure Summary	Logs
variant_quarantine_test should be quarantined when run with variant	A test expected the sum of 2 + 2 to be 5, but it was 4, indicating a failing assertion.	Logs ↗︎

View Full Report ↗︎ ⋅ Docs

[trunk-io]

     

Failed Test	Failure Summary	Logs
variant_quarantine_test should be quarantined when run with variant	A test expected the sum of 2 + 2 to be 5, but it was actually 4, indicating a failing assertion.	Logs ↗︎
variant_quarantine_test should be quarantined when run with variant	A test expected the sum of 2 + 2 to be 5, but it was actually 4, indicating a failing assertion.	Logs ↗︎

View Full Report ↗︎ ⋅ Docs

[TylerJang27]

👍