Use workspace LLM to create thread name

[scottybo]

Pull Request Type

• ✨ feat
• 🐛 fix
• ♻️ refactor
• 💄 style
• 🔨 chore
• 📝 docs

Relevant Issues

resolves #2699

What is in this change?

Uses the workspace's chosen LLM to rename the thread title to something more descriptive, rather than the first sentence of the conversation.

Additional Information

Developer Validations

• I ran yarn lint from the root of the repo & committed changes
• Relevant documentation has been updated
• I have tested my code functionality
• Docker build succeeds locally

[timothycarambat]

#2262 (comment)

The above comment is the primary reason why we dont support this. We offer an application on many various devices and not all of them are capable of concurrent generation or have the resources to do so - which is why the naming is static now since the latency could be high for low-end machines and the UX is not worth it considering that use-case.

Perhaps this could be something that could be done via a system toggle for appearance? This PR in its current form though does not enable that and should not make use of the APIChatHandler as while that works, is a different system that shouldn't be used for text generation in the backend

[scottybo]

Ah - which handler should I be using? Still getting to grips with the code base!

[scottybo]

@timothycarambat I know you're busy, but just wondering if you can give me some insight into which system should be used instead of APIChatHandler?

Also, where would you suggest putting this setting? I'm thinking that each it could be at the workspace level, under Chat Settings, something like this: