Fixed issue with multiple locales in TranslatableMapBuilder

This PR solves an issue with multiple locales of Resource Element. 
Previously only first one localization was set to the database.
this method should be named consistently with its purpose i.e ``addToTranslatedKeys``