feat: parse Oracle RAW(n) and NUMBER(*, s) data types - #2875

DDL exported from Oracle with DBMS_METADATA.GET_DDL spells an INTEGER column as NUMBER(*,0), keeps NUMBER(*,2) as written, and prints binary columns as RAW(16). None of these parse on master, neither in column definitions nor as CAST targets:

CREATE TABLE t (id RAW(16))
  Encountered: <K_RAW> / "RAW", at line 1, column 20
CREATE TABLE t (a NUMBER(*,0))
  Wildcard type arguments are only supported for VECTOR
SELECT CAST(1.5 AS NUMBER(*,0)), CAST(HEXTORAW('AB') AS RAW(16)) FROM dual
  same two errors

Oracle 21c accepts all of them: CREATE TABLE t (a NUMBER(*,0), b NUMBER(*), c RAW(16), d INTEGER, e NUMBER(*,2)) succeeds, and so does the SELECT above. A downstream consumer parsing such exports ran into both.

RAW is a non-reserved keyword token that ColDataType() did not list among its type-name tokens. It is listed now, so RAW(16) is handled like any other identifier type with a length argument, and the other K_RAW uses (FOR XML RAW, DDL parameter lists) are untouched.

NUMBER(*, s) takes the same path as NUMBER(p, s) rather than the generic argument list that VECTOR(*, *) uses since #2845: DataType() accepts * in its precision slot, for NUMBER only, and ColDataType folds it into the type name the way it folds a numeric precision. The scale stays a scale, so both spellings expose the same shape:

NUMBER(5, 0)  getDataType() "NUMBER (5, 0)"  getPrecision() 5     getScale() 0
NUMBER(*, 0)  getDataType() "NUMBER (*, 0)"  getPrecision() null  getScale() 0

The scale slot is unchanged, so NUMBER(*, *) is rejected, and VARCHAR(*) and NUMERIC(3, *) are rejected as before. Neither form is gated on the Oracle dialect; checkGrammarAmbiguity reports no conflicts.

Tests: ColDataTypeTest.testOracleNumberWithWildcardPrecision and testOracleRawType cover the CREATE TABLE, ALTER TABLE ADD and CAST round trips and the NUMBER(*, *) rejection. Both failed with the errors above before the grammar change.