Define how i18n resources are served

Options we have are:

1- let the front grab all the translations and package them in their final artifacts through webpack
2- create a i18n service which can serve the messages (would allow to have a a. UI on top of CRUD@RBAC operations for message editing, b. serve a profile of messages (key -> message) for a language, profile ~= application).

2 is more promishing since it will enable hot reloading for the cloud and still on premise installation (export/import of the profile(s)) but require this new layer to be created, 1 can surely be done through babili somehow.

This task is about defining how we want to handle it and ensure tcomp is friendly with this solution.