[feature] Implement get text like translations

[codesankalp]

Implement get a text like translations: right now translations have to be defined in the configuration file of each organization, repeating the same text over and over, we should avoid this and store the translations in a central place;

However, being able to customize the text for each organization is a great feature and should still be possible if needed.

[nemesifier]

I'd like to ask suggestions from @R9295 with whom I am working on some other project in which we used https://ttag.js.org/ to do this.

Aarnav, here we'll need to do the same thing, with the difference that texts can be overridden by configuration if needed.
If you have any suggestion or recommendation, let us know!

[R9295]

Since there is an express backend, you could lazy load the files that ttag needs (.po.json) depending on the locale, which is ideal. I will think a bit more about dynamic po file generation based on the config.

[nemesifier]

What if we define all strings as placeholders and then have po files for each language, including english?
We could then tweak the code to look for custom po files first, and if the customized versions are found the default po files are ignored.

For example, by default the build process could look for:

1. {languagecode}_{organization_slug}.custom.po
2. {languagecode}.custom.po
3. {languagecode}.po

By default option 1 and 2 will not be provided, but users of this app can prepare a custom po file with different wording if needed (either a general one or one for a specific organization).
That means that by default, option 3 is used.

It would be great if we could allow the custom po files to not be complete duplicates of the original po file, so users would only define the custom strings, this will make it a lot easier to maintain over time.
This could be achieved in the build process by inheriting the translations from the standard files, for example:

• build processes es.po
• if build finds a es.custom.po it compiles it (generates a JSON file with translations and then merges this result on top of es.po)
• if build finds a es_myorg.po it repeats the same process but using as a base the content from es.custom.po