Improve Sunstone translations handling

[MiguelERuiz]

Description Currently Sunstone translations are managed by using a single file that contains the whole content of the translations and texts that appear on Sunstone Application. This began to be too difficult to manage since there is no a good way to put them orderly. So, the enhancement in this is to split this file into different directories to manage specific Translations of each resource. Also, we must to introduce a more formal methodology of translation to indicate more properly the identification of the translation, following the notation is described below:

<resource>.<location>.**<identifier> = <Translation constant>

Here there is a picture that explains more graphically this notation:

Also, it is needed to make some modifications into the script that uploads strings to Transifex in order to recognize the whole new directory structure.

Use case It's going to improve the way new and existing translations are managed

Interface Changes Sunstone constants module, specifically the translates.js file

Additional Context

• [ ] Split translates.js file into new Directory translation structure
• [ ] Add new identifiers to existing translations
• [ ] Modify script that deals with the translations

Progress Status

• [ ] Code committed
• [ ] Testing - QA
• [ ] Documentation (Release notes - resolved issues, compatibility, known issues)