Add missing enum for crate-type in cargo.json

[lsh4711]

The crate-type field in cargo.json carries x-taplo.docs.enumValues with descriptions for all seven crate types, but the corresponding enum array was never present.

Because there are no enum values to attach them to, the descriptions are unused: editors offer no completion candidates for crate-type, and typos such as crate-type = ["cdylibb"] are not reported.

This adds the enum array, matching the seven values already documented in the field description and in the enumValues list (and their order):

bin, lib, rlib, dylib, cdylib, staticlib, proc-macro

Verified locally with Even Better TOML (taplo): completion now offers the seven values, each showing its own description from enumValues, and invalid values are flagged.

Note that cargo itself models crate types as an open set (CrateType::Other(String) in src/compiler/crate_type.rs) and forwards unknown values to rustc, so a future rustc crate type would be reported as invalid until this list is updated. Given that the seven values are already hard-coded in the description and enumValues, that trade-off seems acceptable — but happy to drop this if you would rather keep the field open.

[github-actions]

Thanks for the PR!

This section of the codebase is owned by @ya7010 - if they write a comment saying "LGTM" then it will be merged.

[Copilot]

Pull request overview

This PR updates the cargo.json schema to make the crate-type values for Cargo targets enumerable, so editors can offer completions and validators can flag typos/invalid crate types.

Changes:

• Add the missing enum list for crate-type items, aligned with the existing x-taplo.docs.enumValues documentation.

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.