Fixing packages and Rosetta to provide mostly automatic translation imports

Nowadays translation imports from Rosetta require an awful amount of human administration and work, although in almost all cases all the necessary information can be extracted automatically from package builds through the translation tarballs created by pkgstriptranslations.

We will review the current process, identify cases where human intervention is required, provide solutions for automating them, and review corner cases which should be fixed at the packaging level to make the exported translation tarballs more consistent.