Some tools need to be developed to fully suppport our new localization workflow

See: https://jira.translate5.net/browse/TRANSLATE-5188

See: https://confluence.translate5.net/display/MI/Localization+in+translate5

Needed changes & tools

• add new global function Localization::trans() to localize (-> DONE)
• include translations from ZfExtended_ResponseExceptionTrait::createResponse  (-> DONE)
• Change source-strings in all XLIFFs to EN target, change IDs to MD5 (-> PREPARED, seperate PR)
• Add statistic about new strings / missing translations per language to t5 l10n:update  (-> DONE)
• Move from programmatic localizations in comments to PHP attribute/annotation based ones (->DONE)
• Add resname-atrtributes to trans-units: module & plugin (->DONE)
• The generated Import-ZIPs for localization tasks non EN shall contain the EN localized JSON Files renamed to the desired target-locale. The translation is expected to be done with a TM. This ensures, developers need only to add/amend EN localized json-files (->DONE)
• Add command to autmatically create a localization task for each locale. Task name shall be: translate5-localization-[VERSION] - [locale] (->DONE)
• Add command to automatically import a localization task from translate.translate5.net for the current - and if not found - last version of t5. If not found, the command shall give a selection of the last 5 localization-tasks and automatically import all 4 tasks (-> NOT DONE, will be seperate issue)