Add flag i18nReady

Author: GuoJikun

src/content/docs/develop/Debug/index.mdx

@@ -3,6 +3,7 @@ title: Debug
 sidebar:
   label: Overview
   order: 10
+i18nReady: true
 ---
 
 import CommandTabs from '@components/CommandTabs.astro';

src/content/docs/develop/Debug/rustrover.mdx

@@ -1,5 +1,6 @@
 ---
 title: Debug in JetBrains IDEs
+i18nReady: true
 ---
 
 {/* TODO: Add support to light/dark mode images */}

src/content/docs/develop/Debug/vscode.mdx

@@ -1,5 +1,6 @@
 ---
 title: Debug in VS Code
+i18nReady: true
 ---
 
 This guide will walk you through setting up VS Code for debugging the [Core Process of your Tauri app](/concept/process-model/#the-core-process).

src/content/docs/develop/Tests/mocking.md

@@ -2,6 +2,7 @@
 title: Mock Tauri APIs
 sidebar:
   order: 10
+i18nReady: true
 ---
 
 When writing your frontend tests, having a "fake" Tauri environment to simulate windows or intercept IPC calls is common, so-called _mocking_.

src/content/docs/develop/sidecar.mdx

@@ -2,6 +2,7 @@
 title: Embedding External Binaries
 sidebar:
   order: 1
+i18nReady: true
 ---
 
 You may need to embed external binaries to add additional functionality to your application or prevent users from installing additional dependencies (e.g., Node.js or Python). We call this binary a `sidecar`.

src/content/docs/develop/updating-dependencies.mdx

@@ -2,6 +2,7 @@
 title: Updating Dependencies
 sidebar:
   order: 1
+i18nReady: true
 ---
 
 {/* TODO: Add plugin update example */}