this "naming convention" must be documented

There isn't a forced convention for extension names (as used in the manifest). Chuck defining that convention into the same pile as defining a convention for the extension XML filenames and hope it gets a result.

I have tested this item ? unsuccessfully on 97b7f86

I creted a custom field with superadmin permits
I submited an article as editor.
I had the same result with or without the patch applied

When I tried to save the article I could not because I got the error "Invalid field: campo-editores"

@BertaOctech This PR does not address your issue. Please test PR #22923.

The naming convention is also very important to update a plugin, otherwise the update does not work.

After applying this patch (loadTranslationFiles), I have:
User twister65 installed the plugin PLG_EASYJOOMLABACKUPCRONJOB
It would be better to have :
User twister65 installed the plugin System - EJB Cronjob - Easy Joomla Backup Cronjob

The translation failed.

This pr is just for avoiding the warning at the current code state. Not more.

So I think, you have tested this pr successfully.

I don't think that you can force a naming convention for all these for a long time established extensions without a shitstorm. Would be nice but ...

I have tested this item ✅ successfully on 97b7f86

I have tested this item ✅ successfully on 97b7f86

RTC