ConfigNamesMapper::hasTranslatable has flawed logic

Problem/Motivation

While trying to fix 🐛 Entity view/form mode formatter/widget settings have no translation UI Needs review we stumbled upon a problem with the hasTranslatable method in ConfigNamesMapper. When, for example, we have three config objects to be checked in this method, if one of the config objects does not have translatable items, hasTranslatable returns FALSE for all three config items. Furthermore, hasTranslatable Returns TRUE if no config objects are checked.

Proposed resolution

Reverse the logic of the method, returning TRUE if any of the checked config objects have translatable items, analogous to the hasTranslation method.

Remaining tasks

(reviews needed, tests to be written or run, documentation to be written, etc.)

User interface changes

None.

API changes

ConfigNamesWrapper::hasTranslatable will sometimes now return FALSE where they previously returned TRUE and vice versa. Furthermore, ConfigNamesWrapper::hasTranslatable will now return FALSE when there are no config objects to be checked.

Data model changes

None.