Better error handling in the Chatbot

Problem/Motivation

Currently all errors that gets produced by RAG, Agents or Assistants API are responded as a failed request to the Chatbot and logged in the watchdog with the actual error. The Chatbot will show a "Something went wrong" with a try again button that sends the same request again.

We do not want to show the actual error to the end user since it can be confusing or show error messages the end user is not privy to, so this is on purpose.

Not all errors are the same. Only actual Assistant or Agent errors make sense to retry. Other errors like timeout or out-of-credits errors, should not show the try again button and should rather

Since we have known exceptions for certain events like AiRateLimitException, AiQuoteException etc. we know when some error happens due to technicalities, rather then the Assistant or Agent failing to produce correct JSON for instance.

This means that certain errors where it doesn't make sense to try to retry, where we should just say technical error without a retry button.

Proposed resolution

Change the error message to say only to retry once - if it doesn't work multiple times, it make no sense.
On AiRateLimitException write a message that the its overloaded and they should try later.
On AiQuotaException write a message that there are techincal issues and talk with an administrator.
On AiSetupFailureException write a message that there are techincal issues and talk with an administrator (this should not be able to happen really).
On TimeoutExceptions write that they can either try again or try to rewrite the same instruction but with it creating fewer items (eg. Taxonomy Terms)
Add possibility to overwride these messages with custom messages.