feat: load translations with webpack

[dhhyi]

PR Type

[x] Feature

What Is the Current Behavior?

ngx-translate translation files are loaded with TranslateHttpLoader on the browser side and a special translate loader on the server side. Due to this handling, the translation files are not automatically output-hashed via Angular CLI. This can lead to misbehavior, when new keys are added but the browser still holds the old translation file in the browser cache.

What Is the New Behavior?

• Translation files are consistently loaded via webpack and automatically output-hashed
• The old mechanism of registerLocaleData is exchanged with the new one Doesn't work with FF
• Translation file and Angular locale data is put into its own bundle and pulled when needed.

Does this PR Introduce a Breaking Change?

[ ] Yes
[x] No

[MaxKless]

Hi Danilo, thanks for the PR.
We had some issues with this PR but I see you saw some webpack issues yourself and fixed them. As in #661, we built our own loader during the localization rework (#695). We are not generally opposed to this change. If you want to, you can rebase on our latest release and reimplement these changes. If you decide against it you can close this PR and we will track this enhancement ourselves.
Thanks again!

[dhhyi]

@MaxKless I rebased and put in some refactoring. Please test if everything still works properly.