Add a page on validating a plugin locally before submission

Problem

Many of the checks a plugin goes through during review are automated: manifest.json and submission-requirement validation, and linting with eslint-plugin-obsidianmd. Today there's no page in the docs that explains how an author can run these checks locally before submitting. Authors typically find out about mechanical issues only after a review round-trip, or (worse) after release if something later trips a policy check.

Proposal

Add a "Validate your plugin locally" page under Plugins > Releasing that walks through validating a plugin locally, using the community obsidian-plugin-validator CLI via npx. It would cover:

• What the automated checks are (manifest/submission checks + eslint-plugin-obsidianmd)
• Running the validator with npx, or as a dev dependency / npm script
• The available options and exit codes (for CI use)
• A note that passing locally speeds up review but doesn't guarantee acceptance,
  linking to [[Submission requirements for plugins]] and [[Plugin guidelines]]

Happy to open the PR (page is already drafted) if this is something you'd like added.

• Preview of the Proposed Change/Page

Would you accept this?

Wanted to check first per the contributing guidelines before submitting a PR.

Disclaimer

This is my own npm package, so it's a bit of self-promotion, so I wanted to check/ask before putting up the PR - but, this is an issue I ran into and is on the forums too

Start with the drafted page at en/Plugins/Releasing/Validate your plugin locally.md and verify its npx usage, options, and exit codes against the obsidian-plugin-validator CLI. Ensure it explains manifest and submission checks, eslint-plugin-obsidianmd, and CI usage, with links to Submission requirements for plugins and Plugin guidelines; done when the page is complete and accurate.