feat(nf): Angular i18n support

[refactorTractor]

closes #413

Angular i18n support in native federation

This is how i18n support could play out in my opinion:

• Shared entries/packages build just as they used to.
• Exposed entries are built by the angular application internal builder
• index.html-s are found in the build output, and each transformed
• remoteEntries are copied next to index.html-s found, and transformed for the new directory structure
• a remoteEntry is created in the top directory that has the references to each language bundle's exports as well
• to match physical paths with urls in basehref-s you can provide pathMappings that will do the transformation in dev server mode.

There is no need to modify the nf-core project (or the runtime)

[aramirezj]

Hey! Would you be able to provide steps to try your fix?

I have tried:

1. Cloning and installing your branch
2. Generate the bundles
3. Clone the native module federation from manfred at 17.2 version, and install the dependency from your forked branch
4. I have tried to add i18n and generate the locales with the builder @angular-devkit/build-angular:extract-i18n but it does not go through for some old error An unhandled exception occurred: The "paths[1]" argument must be of type string.

If not, if you could provide a repository with your solution applied so it can be tested it would be amazing

[Ooi-Jun-Xiang]

Hey @aramirezj

I think the issue regarding i18n he meant is when building the whole project that has i18n, not when compiling i18n only(extract-i18n). As for the error you get on 4, you can change the buildTarget to <project>:esbuild instead of <project>:build, although I am not sure why there will be error in the <project>:build. Anyways, I hope that this PR get merged, as I also need it in my project.

 "architect": {
     "build": {
         "builder": "@fork-fork/native-federation:build",
         ...
     },
     "extract-i18n": {
         "builder": "@angular-devkit/build-angular:extract-i18n",
         "options": {
-            "buildTarget": "<project>:build"
+            "buildTarget": "<project>:esbuild"
         }
     },
     "esbuild": {
         "builder": "@angular-devkit/build-angular:application",
         ...
     }
 }