Describe the Bug

Hi Directus team,

Adding a translations field to any collection will always result in Directus automatically creating a new "languages" collection and in another request try to fill that with preset items, like the following:

[ { "code": "en-US", "name": "English", "direction": "ltr" }, { "code": "ar-SA", "name": "Arabic", "direction": "rtl" }, { "code": "de-DE", "name": "German", "direction": "ltr" }, { "code": "fr-FR", "name": "French", "direction": "ltr" }, { "code": "ru-RU", "name": "Russian", "direction": "ltr" }, { "code": "es-ES", "name": "Spanish", "direction": "ltr" }, { "code": "it-IT", "name": "Italian", "direction": "ltr" }, { "code": "pt-BR", "name": "Portuguese", "direction": "ltr" } ]
That is very kind of Directus, but I have my own Languages collection already. And the internal /collections call as well as the /fields call will come back as 500 anyways. The thing is: Receiving the message inside the GUI is quite confusing because one expects there was something wrong creating a new translations field (which is not the case)
Maybe there should be an option to disable this feature. Thanks!

To Reproduce

You should have your own languages collection

1. Create a new collection
2. Create a new field and use the "translations" Schema > Set your own Languages collection, Language Indicator and Language direction fields > save
   => Use the dev tools to inspect what is going on

Directus Version

v10.8.1

Hosting Strategy

Self-Hosted (Docker Image)