Fallback to ai_translate configuration

I think this config screenshot makes sense (MR does this):

MR doesn't actually function yet. I would like to see where this issue goes 📌 Discuss: Unify translate operations over ai Active as it could provide a service to call as well which perhaps we can use at the last moment (still us handling chunks to match TMGMT).

Okay its working now with 📌 Discuss: Unify translate operations over ai Active - probably some coding standards to clean up. But first we need that issue there resolved and there are some critical issues that are blockers still for it, for example it returns escaped html, so we cannot use it here yet.

OK very exciting! I'm ready to test when it's ready to test :)

Looks like we are almost there in the AI module itself.

If anyone wants to test locally, you can:

1. Apply this merge request
2. Apply the merge request from 📌 Discuss: Unify translate operations over ai Active to the AI module
3. Enable AI Translate sub-module of AI module
4. Run `drush updb`
5. Visit /admin/tmgmt/translators/manage/ai and select "Use the configuration from the "AI Translate" module (recommended)"
6. Visit /admin/config/ai/ai-translate and edit your prompts from the AI module

Okay ready to merge as soon as there is a new release containing 📌 Discuss: Unify translate operations over ai Active