fix: don't block StatusMessageWatcher exit with 6s sleep on exception

[vdusek]

Summary

StatusMessageWatcher sleeps 6 seconds on exit to let the final status/status-message propagate. Two issues with the current placement:

• API asymmetry: the sync stop() does the sleep itself, while the async twin does it in __aexit__. So manual sync stop() paid the 6s even though manual await stop() did not.
• Exceptional exits were delayed: both __exit__ and __aexit__ ignored the exc_type they receive, so a Ctrl+C or any exception bubbling out of with/async with was held up 6 seconds.

This change:

• Moves time.sleep(self._final_sleep_time_s) out of sync stop() into __exit__ (matches async shape).
• Gates the sleep in both __exit__ and __aexit__ on exc_type is None so exceptional exits propagate immediately.

Normal-exit behavior (the final-message capture window) is preserved.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 95.24%. Comparing base (6b8001e) to head (aa6aa40).
⚠️ Report is 7 commits behind head on master.

Additional details and impacted files

@@            Coverage Diff             @@
##           master     #753      +/-   ##
==========================================
- Coverage   95.45%   95.24%   -0.22%     
==========================================
  Files          45       45              
  Lines        5125     5127       +2     
==========================================
- Hits         4892     4883       -9     
- Misses        233      244      +11     

Flag	Coverage Δ
integration	95.24% <100.00%> (-0.22%)	⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 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.