[Tech Docs December Launch] TR for navigation.yaml update [ongoing]

Goal

Cover weekly updates for navigation.yaml file for December launch.

Every new request can be wrapped into a task for now until we decide how to proceed with continuous loc for this file.

Test an optimal turnaround time with Argos team that would cover:

• AI script translation
• QA checks both automated and linguistic
• Human Review

Notes: this file has a good TM leverage, which should help in achieving a quick turnaround

Results and conclusions:

Important: always wait for the asset to be merged upstream (+ another 12-24 hours) before re-pushing the asset for updates. This helps to avoid having merge conflicts down the road. Our fork main-translation gets updates pulled down from master (upstream), and if we don't wait for this reconciliation to occur and are too quick with re-pushing the assets through Argo, it is very likely we will run into a merge conflict in the upcoming Translation MRs for this asset. Relevant slack.