Fix release workflow: exclude vscode-objectql from npm publishing

[Copilot]

The release workflow fails when attempting to publish vscode-objectql to npm. VSCode extensions should only be published to the VSCode Marketplace via vsce, not npm.

Changes

• Add vscode-objectql to the ignore array in .changeset/config.json

This prevents changeset from attempting to publish the VSCode extension package to npm while allowing all other @objectql/* packages to publish normally.

{
  "ignore": ["vscode-objectql"]
}

The VSCode extension can be published separately to the marketplace using its existing vsce publish workflow when needed.

Original prompt

引用: https://github.com/objectstack-ai/objectql/actions/runs/21085726694/job/60648624317#step:8:1

---

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.

[github-actions]

⚠️ No Changeset Found

This PR does not include a changeset file.
If this PR includes user-facing changes, please add a changeset by running:

pnpm changeset

[Copilot]

Pull request overview

This PR fixes a release workflow failure by preventing the vscode-objectql VSCode extension from being published to npm. VSCode extensions should only be published to the VSCode Marketplace using vsce, not to the npm registry.

Changes:

• Add vscode-objectql to the ignore array in .changeset/config.json to exclude it from npm publishing