[Translation] Process enhancement

Collecting here the list of known improvements required to streamline the current translation process.

Users (simplified):
- Alicia manages via an agency the list of pages that should be "deployed" in new countries / regions
- Kitty manages the translation process and translation agencies
- Priyal is responsible for the EN content

Current status:
1. to kick-off a translation batch, Alicia creates an Excel spreadsheet in Sharepoint ("tracker file" - can be stored in the drafts folder - location does not really matter)
1. she lists all the URLs to be translated and the "languages" (locales...) to be translated into.
a. supported languages for GLaaS: [tracker config file](https://adobe.sharepoint.com/:x:/r/sites/FedsPublishing/_layouts/15/Doc.aspx?sourcedoc=%7B355C3C83-AE34-4D6E-9C71-DE66673524A1%7D&file=trackerconfig.xlsx&action=default&mobileredirect=true)
b. [sample tracker file](https://adobe.sharepoint.com/:x:/r/sites/FedsPublishing/_layouts/15/Doc.aspx?sourcedoc=%7BCDAD4A59-8562-43DF-8C28-9495C51A6620%7D&file=7174_Helix_WS_Pilot_Demo.xlsx&action=default&mobileredirect=true)
1. once ready, Alica can open the sidekick and hit the "Translate from Tracker" button. The tool shows a summary of what is going to happen (list of pages and languages to be translated into).
1. From there, Alicia can hit the "Send to Translation" button. This will create the corresponding translation tasks in GLaaS and WorldServer.
1. Once the translation process is done, Kitty sends a mail to Alicia. Alicia can then "download" the translated files, i.e. they are saved in Sharepoint in a folder with the same name than the original tracker file. Files can then be reviewed and moved to their "production" folders.

Current flaws:
1. the quality of the original files is not optimal
a. some headers are wrong, styling not perfect
b. the name of the metadata must not be translated
c. comments must be removed (version history is fine)
1. Users are confused by "languages" for translation vs locales vs baby regions (`be_fr` is french for Belgium but GLaaS only knows fr_fr as for french)
1. Links must be adjusted (i.e. ...adobe.com/en/... -> ...adobe.com/fr/...)
a. this is today done manually by the translation agencies as an extra step. This should not be their responsibility.
1. once the files are saved into drafts, they must be copied manually from drafts to their final locale destination.

Improvements:

- [x] EN content cleanup
a. this is a cleanup task which is already happening. Check styles in all files, apply a DNT (Do Not Translate) style for the metadata, remove comments...
- [ ] #130
- [ ] #131
- [ ] Save files directly in the "production" environment
a. if the EN source files are clean and URLs auto adjusted, no manual step should be required

Start by reviewing the sidekick workflow behind “Translate from Tracker” and “Send to Translation,” along with the tracker config and sample tracker links. Clarify the scope of #130, #131, URL adjustment, locale mapping, and direct production saves before locating implementation entry points. Done means the agreed translation-process improvements are implemented and verified end to end.

Written by the indexing model from the issue text.