Complete Arabic localization with UI strings and RTL configuration

[aslamalkarywk7]

Summary

This PR introduces full Arabic localization for the InvokeAI documentation suite. It features the translation of the core documentation pages, UI localization strings, and configures the layout for Right-to-Left (RTL) reading orientation.

• Kind of change: Documentation (docs) / i18n
• The "Why": To make InvokeAI accessible to the Arabic-speaking developer and creator community, expanding the project's global reach.
• The "How":
  • Translated and added 62 MDX documentation files under docs/src/content/docs/ar/.
  • Added core UI localization keys inside src/content/i18n/ar.json.
  • Configured the Arabic locale metadata with dir: 'rtl' inside astro.config.mjs.
  • Included all localized high-resolution asset images and banners.

Related Issues / Discussions

• Supersedes and replaces the closed PR Translate InvokeAI documentation to Arabic for Arab developers #9282.

QA Instructions

I have thoroughly tested the documentation build locally to ensure a seamless layout:

1. Ran the local Astro Starlight development server using pnpm dev.
2. Verified the entire Arabic (/ar/) documentation path.
3. Confirmed that the typography, sidebar navigation, and search layout adapt perfectly to the Right-to-Left (RTL) alignment.
4. Checked that all absolute/relative image paths render properly without broken links.

Merge Plan

This is a large PR containing documentation files and assets only. It does not touch any core application logic, DB schemas, or code repositories. It can be safely merged once the documentation CI checks pass.

Checklist

• The PR has a short but descriptive title, suitable for a changelog
• Tests added / updated (if applicable)
• ❗Changes to a redux slice have a corresponding migration
• Documentation added / updated (if applicable)
• Updated What's New copy (if doing a release after this PR)

[aslamalkarywk7]

Hi @joshistoast and @lstein,

I noticed that the CI build (check-and-build) failed due to a missing relative asset path (cuda-sysmem-fallback.png) inside the newly translated Arabic file low-vram-mode.mdx.

I am currently fixing this path mapping issue and will push the update shortly to get the workflow checks passing. Sorry for the oversight!

[joshistoast]

1. High: Arabic pages link back to English docs via root-relative URLs.**
   docs/src/content/docs/ar/index.mdx:81, docs/src/content/docs/ar/features/gallery.mdx:135, docs/src/content/docs/ar/contributing/index.md:13
   I found 38 root-relative internal links like /start-here/installation/, /concepts/prompting-guide/, and /development/. From an Arabic page these navigate to the default English locale instead of /ar/..., so users fall out of Arabic navigation. Use relative links or prefix internal absolute links with /ar/.

2. Medium: Several relative links resolve to non-existent nested routes.
   Examples:
   docs/src/content/docs/ar/features/Canvas/shapes-tool.mdx:28 uses ./lasso-tool/, which resolves from /ar/features/canvas/shapes-tool/ to /ar/features/canvas/shapes-tool/lasso-tool/.
   docs/src/content/docs/ar/features/Multi-User Mode/user-guide.mdx:321 uses ./api-guide/, resolving to /ar/features/multi-user-mode/user-guide/api-guide/.
   docs/src/content/docs/ar/features/Workflows/editor-interface.mdx:16 uses ../../concepts/diffusion, resolving to /ar/features/concepts/diffusion.
   These should use sibling/ancestor-correct paths such as ../lasso-tool/, ../api-guide/, and ../../../concepts/diffusion.

3. Medium: Sidebar group labels remain English in Arabic locale.
   docs/src/config/sidebar.ts:8, docs/src/config/sidebar.ts:16, docs/src/config/sidebar.ts:24
   The PR adds ar to Starlight locales, but the sidebar section labels are hard-coded as English: Start Here, Configuration, Concepts, etc. Arabic page titles are translated, but the main navigation categories will still be English.

4. Low/Medium: Arabic assets duplicate existing assets byte-for-byte.
   docs/src/content/docs/ar/assets/*
   The PR adds about 15 MB of duplicate images under ar/assets; every checked image matched an existing English asset by SHA-256. Unless localized screenshots are planned, this bloats the repo and build inputs unnecessarily. The Arabic docs can reference the existing asset locations instead.