chore: use the combined Lua tooling workspace

[ChatDisabled]

Changes

Use the combined qbx-lint Cargo workspace for editor development, CI, bundled-server release builds, resource fixtures, and Zed downloads. The separate language-server checkout is no longer required; the executable and archive names remain qbx-lua-ls.

Uses the workspace migration merged in Qbox-project/qbx-lua#8 and updates all editor/Zed manifests to 1.0.5 for the first shared release. Old linter tags do not contain the server crate or server release assets. The contribution guide and editor setup instructions document the new checkout paths and cutover order.

The first shared tooling release must be available before merging and publishing this editor release so Zed can download the server from its new location.

Checks

• npm run typecheck, npm run build, and the full VS Code integration suite passed on Windows with the server built from the combined workspace.
• python -m unittest discover -s scripts -p 'test_*.py': all seven Marketplace verification tests passed.
• Zed: formatting, Clippy for wasm32-wasip2, and the Wasm release build passed.
• GitHub CI passed the full VS Code integration suite on both Ubuntu and Windows, and the Zed checks.
• Actionlint passed for CI and release workflows; both retain the existing platform coverage.
• npm run package -- --target win32-x64: the VSIX packaged successfully, contains the exact new workspace server binary, and installed successfully into an isolated VS Code test profile.

No Marketplace release was published during validation. Linux/macOS packaging and interactive Zed testing were not performed locally.