GeezerVison

For DuckDB's star expression modifiers (docs) and trailing commas in the select list (docs).

• ColumnsTransformer gains getRenameItems() and isParenthesized(). The unparenthesized forms are only recognised after * / t.*, as in DuckDB. REPLACE item needs an AS at its top level and RENAME needs column AS name for every column, so * rename / * replace stay aliases of the star and ClickHouse's REPLACE STRICT checks are unchanged.
• Behaviour change: * REPLACE (a + 1) AS a is now DuckDB's single item (a + 1) AS a; it used to be an unaliased REPLACE(a + 1) with the star aliased a, which no dialect accepts.
• The trailing comma is accepted before ), FROM, WHERE, HAVING, WINDOW, INTO, a set operator, GROUP BY/ORDER BY with an expression, and LIMIT/OFFSET followed by a number or ?. Columns and functions named after keywords keep parsing: SELECT a, limit FROM t, SELECT a, limit(1) FROM t, SELECT a, group by FROM t. A comma at the end of the input stays an error, and SELECT 1, LIMIT ALL is still a column. It applies wherever a select item list is parsed (RETURNING, PIVOT ... IN, DISTINCT ON, ...).
• Apart from the REPLACE case above, all new inputs were errors in every dialect; on ~6,700 statements extracted from this repository's tests, results are identical to master.
• checkGrammarAmbiguity: no conflicts. ./gradlew check: 10,118 tests, 0 failures.
• DuckDB's own test suite (test/sql, 70,729 statements): 146 more parse, none less.