Translation push for documentation

What does this MR do and why?

Describe why, not just what. Include links to relevant issues or discussions.

This MR pushes all available translations from the main-translation branch of our production fork to the upstream GitLab Docs repository.

Changes Overview

1. Adds translated content for documentation pages
2. Ensures consistent formatting across all translated files
3. Maintains directory structure alignment with the original English content

Related gitlab-com/localization/docs-site-localization#174 (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

Numbered steps to set up and validate the change are strongly suggested.

1. Configure a local GitLab Docs environment.
2. Check out this branch.
3. Format the ja-jp.yaml incorrectly
4. Run make lint-yaml to verify that it will fail on a change out i18n yaml. This confirms the lint:yaml CI job is working correctly, and the yaml passes.
5. TBD - confirm locales/ja-jp.json is linted
6. Run the site locally, to confirm it's functional and working with these translation changes. Since Hugo is not configured to build the /ja-jp/ path yet, these files are not used and therefor not impact the site currently. Confirm this locally and in the review app!

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.