[WIP] Fix debugger triggering on Ctrl-C during deployment

[Copilot]

• Understand the code flow for AI debugger triggering
• Identify where context cancellation should be checked
• Modify handleTailAndMonitorErr to check for context cancellation before triggering debugger
• Modify handleComposeUpErr to check for context cancellation before triggering debugger
• Modify compose up and config commands to check for context cancellation on load errors
• Add tests for context cancellation scenarios
• Build and test the changes
• Run code review and security checks

Original prompt

---

This section details on the original issue you should resolve

<issue_title>Ctrl-C during deployment (up/down/destroy/cd…) should not trigger debugger</issue_title>
<issue_description>When the user cancels the CD operation by pressing ctrl-c (context canceled) we should not trigger the AI debugger.

</issue_description>

<agent_instructions>Before triggering the AI debugger, check whether the operation was aborted because of context cancelation. </agent_instructions>

Comments on the Issue (you are @copilot in this section)

• Fixes Ctrl-C during deployment (up/down/destroy/cd…) should not trigger debugger #1692

---

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.