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)