Improve i18n corrupted file resiliency

When i18n JSON files have been corrupted, for instance through git direct access, neither the release or the project can be build. The exception is thrown and not managed which lead to an unknown error message for the end-user; meanwhile this behavior is not consistent with the current build behavior that's skipping/ignoring faulty feature.

Goal of this ticket is to align the i18n build behavior with the rest of our builders, and ensure the project is still building/releasable if the i18n is not parseable.