ConfigNamesMapper::hasTranslatable() logic was fixed

ConfigNamesMapper::hasTranslatable() previously had two logic flaws:

1. If no config names were registered in the mapper it would return TRUE. This does not make sense, because if nothing is contained in the mapper certainly nothing has translatable data.
2. If multiple config names were registered in the mapper it would only return TRUE if all of the config names have translatable data. This does not make sense, because surely if one of the things in the list contains translatable data then the list as such does too.

The second bullet point was even documented on ConfigMapperInterface::hasTranslatable() and tested but it is still wrong.