Add navapp to l10n translations module

Although the Navigation Application is not part of the XM release train we can use the translation tooling and XM release cycle to update the translations. Current solution

• The navapp resources are deployed as Maven resource
• The cms-translations always depends on a tagged version of the navapp resources
  • After translation is done resources are copied (manually) to the navapp for stand-alone usage
  • Deploy is skipped for the navapp l10n module

Pro: We can use one mechanism to send and retrieve translations

Con: Requires scheduling the translations so there is time to include translations in navapp. Worst case need to translate twice

Con: Manual step to copy the translated jsons into the navapp

Big drawback is