Refactor and update translation template location

What does this MR do and why?

This MR moves the location for Localization specific Translation Templates (that gets only used by a vendor specific tool-chain Argo) and move it out of the Merge Request templates directory.

Here's what's done:

1. Planning to remove both of the Translation Templates out of the Merge Request Templates directory - to reduce the possibility of accidental usage by a human. These templates are only used by Argo and have specific Argo placeholders in them. Since the some configuration in Argo may still use the old location, as for this initial iteration, we are only removing one of the templates and leaving the other one for now (see this thread for more details).
2. Refactored the template "Documentation Localization AI.md" to make it human readable as identified previously. This template has also been renamed as suggested by @jcole-ext in this thread.

Related

• Related to
  • gitlab-com/localization/docs-site-localization#888 (closed)
  • gitlab-com/localization/docs-site-localization#911 (closed)
  • gitlab-com/localization/docs-site-localization#906 (closed)

Screenshots, screen recordings, or links to review app

These are strongly recommended to assist reviewers and reduce the time to merge your change.

How to set up and validate locally

No separate validation is required. We can safely test this out through Argo dashboard/UI, once merged - similar to how it was done here.

Merge request acceptance checklist

This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.

• I have evaluated the MR acceptance checklist for this merge request.
• If this MR changes how markdown is interpreted, share this MR in the #tech-docs-localization slack channel. The translation tooling might need to be updated, for example if new syntax is added or existing syntax rendering is changed.