💡 [Feature]: Improve /manage chat command behavior

[Adam-it]

🎯 Aim of the feature

Sometimes we may not get any response from the /manage chat command even though the response was present or the error message would provide more context to help the dev. We may correct the following

• 💡 [Feature]: improve /manage chat command so that it uses text output modes for all list CLI for M365 command types #375
  What we could do is use output text for list commands which usually may return a lot of rows
• 💡 [Feature]: Improve /manage chat command to show response error message #376
• 💡 [Feature]: Add more support to other areas of Microsoft 365 like OneDrive or Teams ot the /manage chat command #377

📷 Images (if possible) with expected result

🤔 Additional remarks or comments

No response

[nicodecleyre]

Can i work on this one?

[Adam-it]

Can i work on this one?

Sorry @nicodecleyre but I think I forgot to update this issue.
Let's put this on hold until I finish #344
Which I am currently investigating.
When we refactor the chat participant to use prompt-tsx it the logic will be totally different than now as we will define prompts in tsx.
Also this will get us unblocked in managing priortizations in long prompts and chunking in long prompts which in current implementation is not supported.

May I kindly as you for now to pick a different issue 🙏.
Sorry for the confusion

[Adam-it]

closing this as I extracted the points in this issue to smaller separate issues so that we may have some work unblocked