[FEAT] Generic translation endpoint to replace Customized LibreTranslate

[NeonDaniel]

Objective

Implement a /translate backend to replace calls currently made to a custom LibreTranslate container.

Initial Implementation Requirements

• /translate/simple endpoint that accepts text, input_lang, and output_lang. Input lang of None should use lang detection. text may be a single string or a list of strings; return value is a list of strings
• /translate/detect endpoint that accepts text input and returns lang and languages values with most likely language and optional a list of (lang, conf) tuples
• /translate/bulk endpoint that accepts inputs (List[str]), input_lang (str) and output_langs (List[str]) and returns a dict of lang to a list of translated strings
• This must be implemented such that translation plugins are interchangable

Other Considerations

• This may be implemented in ovos-translate-server, OR here with an accompanying connector to load translation plugins and connect them to the MQ bus
• Klat currently uses MQ directly to get bulk translations
• Neon should be updated to use whatever hosted solution this implements by default

[NeonDaniel]

Currently, STT and TTS plugins are hosted independent of HANA. I think that either:

• Translation plugins are treated the same and we do not add a HANA endpoint for this, with all changes going to ovos-translate-server OR
• We decide to add equivalent endpoints to HANA (not immediately) that enable STT and TTS plugin access.

The latter option does raise questions about hosting multiple plugins in one backend, but does expose a unified endpoint for all hosted services. Deferring to OVOS server packages means it is less clear where different endpoints exist, but does scale more easily where hosting multiple services is desired.

In any case, the MQ integration Klat uses for translations will likely need to be updated or replaced with an HTTP query

[NeonDaniel]

Relevant Klat integration changes in LibreTranslate

This also includes an example for how services could be attached to MQ as well as the example inputs from Klat that need to be supported

[NeonDaniel]

Currently, STT and TTS plugins are hosted independent of HANA.

Also worth noting that LLMs hosted by Neon are also similar in that they use vLLM and expose their own endpoints.