fix(jq): support quoted string key shorthand in object construction

[skoblenick]

Problem

The jq parser did not support quoted string key shorthand syntax in object construction. In real jq, {"name"} is valid shorthand for {"name": .name}, allowing users to quickly project fields from an object. Our parser required a colon and explicit value after every quoted string key, causing expressions like {"name"}, {"name", "label"}, and keyword keys like {"if"} to fail with a parse error.

This broke real-world pipelines such as:

echo '{"id":"abcde","name":"foo","label":"bar"}' | jq -c '{"name", "label"}'
# Expected: {"name":"foo","label":"bar"}
# Got: parse error

Fix

Updated the query-engine parser (src/commands/query-engine/parser.ts) to handle quoted string keys the same way as unquoted identifier keys: when a quoted string key is not followed by a colon, it is treated as shorthand — the key becomes the string value and the value becomes .key (a field access). When a colon follows, the existing explicit key-value behavior is preserved.

Tests

• Unit tests (src/commands/jq/jq.string-key-shorthand.test.ts): 21 tests covering parser AST correctness and evaluation for standard keys, keyword keys ("if", "true", "null", "as", "try"), non-identifier keys ("a-b"), numeric string keys ("1"), empty string keys (""), mixed shorthand + explicit entries, and fromjson pipelines.
• Comparison tests (src/comparison-tests/jq.comparison.test.ts): 8 tests validating output parity with real bash jq across all shorthand variants.

[vercel]

@skoblenick is attempting to deploy a commit to the Vercel Labs Team on Vercel.

A member of the Team first needs to authorize it.