I18nFileLoadError for locales ‘am’ and ‘ml’ due to Misidentification in load_directory

### Body
Hello,

When the user's locale is set to 'am' or 'ml', the code in the `load_directory` function of `resource_loader.py` incorrectly assumes that a corresponding localization file exists. This leads to an `i18n.loaders.loader.I18nFileLoadError`. The error message displayed is:

```plaintext
I18nFileLoadError: error getting data from resources/translations/de.yaml: ml not defined
```

This issue arises due to improper file existence checking. The locales 'ml' and 'am' are mistakenly identified as existing because they are substrings of the ".yaml" file extension. This results in the erroneous assumption that the relevant localization files are present.

#### Suggested Fix
A more robust method of checking for the existence of localization files should be implemented to prevent substring matches within file extensions.

Inizia in resource_loader.py, nella funzione load_directory, e riproduci il problema con le locale 'am' e 'ml'. Esamina come vengono controllati i nomi dei file di localizzazione, quindi verifica che questi nomi di locale non vengano identificati come sottostringhe dell’estensione .yaml e che l’erroneo I18nFileLoadError non si verifichi più.

Scritto dal modello di indicizzazione a partire dal testo della issue.