Translation Integration Framework: Support i18n dictionary translation

[#1]

Request for Feature Enhancement (RFE) Summary:	Add support for translation of i18n dictionary again to translation framework in order to send out those to translation agencies in an automatic manner like for page content.
Use-case:	We want to sent out i18n values not manually but automatically using the integrated translation framework.
Current/Experienced Behavior:	In AEMaaCS the option to add i18n dictionary is not available anymore. This is obviously not possible as /apps path is immutable content now. This means we have to translate values manually which is not efficient.
Improved/Expected Behavior:	We used to send out i18n dictionaries on Adobe AMS using the integrated translation framework to have an automatic and efficient way like for pages. Please bring back this option to make the process as efficient as possible.
Environment Details (AEM version/service pack, any other specifics if applicable):	AEMaaCS
Customer-name/Organization name:	Carl Zeiss AG
Screenshot (if applicable):
Code package (if applicable):

ams_translationjob.png ‏10 KB

cloud_translationjob.png ‏18 KB

[#2]

@lutzU 

Thanks for proposing this idea.

This has been reported to the engineering under the internal reference SITES-23486. The product team will triage this request to verify feasibility based on the prioritization model. This post will be updated according to the Jira status.

[#3]

@lutzU This is a duplicate of [1]. This is already in the pipeline. 

[1]https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager-ideas/authoring-ui-for-i18...