fix(duckdb): Fix NOT precedence for JSON extractions

[kyle-cheung]

When running a query like WHERE NOT json -> 'key', DuckDB attempts to apply the NOT to the entire JSON before performing the extraction. This results in a Conversion Error because the JSON string cannot be cast to a numerical/boolean type for negation.

Wrapping the JSON extraction in parentheses resolves the error.

CREATE TABLE test_json AS SELECT JSON '{"is_active": false, "is_true": true}' AS data;

-- Will fail
SELECT * FROM test_json WHERE NOT data -> 'is_active';

-- Will work
SELECT * FROM test_json WHERE NOT (data -> 'is_active');

This is expected to take higher precedence in a future DuckDB release (expected 1.7.0) see here duckdb/duckdb#20399

[georgesittas]

Hey @kyle-cheung, thanks for the contribution.

A minor request on my end, should be good to go otherwise.