What this PR does

Before this PR:

• No Zed editor configuration example existed for contributors using Zed
• Several config files had inconsistent JSON array formatting
• biome.jsonc had redundant exclude rules
• Contributing guides did not reference the development guide
• development.md (zh) was not translated to Chinese
• Node.js and pnpm versions were hardcoded in the development guide

After this PR:

• Added .zed/settings.json.example with Biome formatter, oxc/eslint/biome fixAll, and import organization
• Cleaned up redundant Biome exclude rules and unified JSON array formatting
• Added "Setting Up Your Development Environment" section to CONTRIBUTING.md (en/zh) linking to the development guide
• Added Zed editor setup guide to development.md (en/zh)
• Translated docs/zh/guides/development.md to Chinese
• Node.js version now references .node-version; pnpm version references packageManager in package.json
• VSCode extensions now reference .vscode/extensions.json

Why we need it and why it was done in this way

The following tradeoffs were made:

• The Zed settings file is provided as an .example rather than a direct .zed/settings.json to avoid overriding individual contributor preferences.
• Versions reference their source of truth files rather than being hardcoded, so docs stay in sync automatically.

The following alternatives were considered:

• N/A

Breaking changes

None

Special notes for your reviewer

• The JSON formatting changes are purely cosmetic — no behavior changes. They align with Biome's default formatting rules.
• The .zed/settings.json.example includes source.fixAll.eslint and source.fixAll.oxc alongside Biome, matching the project's triple-linter setup.

Checklist

• PR: The PR description is expressive enough and will help future contributors
• Code: Write code that humans can understand and Keep it simple
• Refactor: You have left the code cleaner than you found it (Boy Scout Rule)
• Upgrade: Impact of this change on upgrade flows was considered and addressed if required
• Documentation: A user-guide update was considered and is present (link) or not required. Check this only when the PR introduces or changes a user-facing feature or behavior.
• Self-review: I have reviewed my own code (e.g., via /gh-pr-review, gh pr diff, or GitHub UI) before requesting review from others

Release note

NONE