add last 30 terminal outputs for tracking for errors on command

[nullfunc]

Description

When CLI errors occur we don't always have a good idea of why it happens as we do not have customer deployment information. By including the last 10 lines of their terminal output when an error occurs on a command or before the AI debugger prompt we can hope to get some context on why they have a failure.

This PR includes

• adding a circular buffer to the terminal to cache the last 10 terminal outputs
• add the terminal output to tracking command events which has a failure
• add the terminal output to tracking of when the debugger prompt

Linked Issues

fixes #2291

Checklist

• I have performed a self-review of my code
• I have added appropriate tests
• I have updated the Defang CLI docs and/or README to reflect my changes, if necessary

[jordanstephens]

As discussed, these argument lists are getting long and threading the cache through each layer is adding a lot of complexity. I think this is getting complex enough to warrant creation of a log client struct that can has properties for the provider client and the cache. But given how many of us are working in this code right now, I think its best to do this in isolation in a followup.

[nullfunc]

Update: This PR is on hold. As mentioned above the threading of the logCache and the size of some of the function signatures is cumbersome. Additionally, this may not be the best way to log build breaks for analysis.