indication if AI mode is properly configured

[fwild]

provide some feedback on all the pitfalls - like credit running low, microphone off, etc.

[AKissMail]

I would take out the credit aspect since that is nothing that we want to expose to the User and a lack of design is also blocking. I can add that to the existing UI but would be nice to have a design and make it more final.

[AKissMail]

We could take the low credit in to that ticket:

https://github.com/WEKIT-ECS/lxr/issues/66

[AKissMail]

Hi @fominykh, I have worked through the code and believe we need UI elements to communicate the following five events:

1. An audio clip is empty or null: This typically indicates an issue with microphone permissions. The AiServicesAudioClipIsEmpty event is triggered in such cases.
2. Message to an LLM/RAG or a TTS model is empty: The AiServicesMessageIsNull event is triggered in this scenario. Currently, this happens only if the recording fails. However, if we add a mode to chat via a keyboard, this could occur independently as well.
3. Bad configuration of a VI or other model: The AiServicesConfigurationIsBad event is triggered in such cases, indicating that something is wrong with the lesson or configuration.
4. User session issues: The AiServicesLoginFailed event is triggered if the user session has expired or the user has not logged in.
5. Generic HTTP request failures: The AiServicesHttpRequestFailed event covers all issues not addressed above. These may include no internet connection, internal server errors, or unavailable servers. This event should prompt the user to verify their internet connection. If the issue persists, a support ticket should be opened.

The events are already implemented and pushed to this branch