CTE parsing fails when name is a non-reserved keyword

先執行兩個 vendor/bin/sql-parser --lint --query 重現案例，並追蹤 lexer 和 parser 如何處理 WITH 後的 CTE 名稱，包括以反引號引用的名稱。完成的判定標準是兩個查詢都能成功剖析，包括非保留關鍵字名稱和加引號的關鍵字名稱，且不出現回報的錯誤。

The parser rejects valid CTEs whose names are non-reserved keywords, throwing:

The name of the CTE was expected.

MySQL has a large set of keywords that are explicitly not reserved (no (R) marker in the official MySQL 9.7 keyword list^1). Non-reserved keywords are explicitly permitted as unquoted identifiers, including CTE names. MySQL executes these queries without error^2.

Reproducer

Unquoted:

vendor/bin/sql-parser --lint --query "WITH data AS (SELECT 1) SELECT * FROM data"

#1: The name of the CTE was expected. (near "data" at position 5)
#2: Unexpected end of the WITH CTE. (near "data" at position 5)
#3: Unrecognized statement type. (near "data" at position 5)

Backtick-quoted (which should unconditionally allow any keyword as an identifier):

vendor/bin/sql-parser --lint --query "WITH `data` AS (SELECT 1) SELECT * FROM `data`"

#1: The name of the CTE was expected. (near "`data`" at position 5)
#2: Unexpected end of the WITH CTE. (near "`data`" at position 5)
#3: Unexpected beginning of statement. (near "`data`" at position 5)
#4: Unrecognized statement type. (near "AS" at position 12)

Expected behaviour

The query parses successfully for any non-reserved keyword used as a CTE name, whether unquoted or backtick-quoted.

Actual behaviour

Parser throws errors in both cases. The root cause appears to be that the lexer classifies all keywords as keyword tokens unconditionally, rather than resolving them contextually. After WITH, the parser expects an identifier token; receiving a keyword token instead, it fails, even though MySQL allows non-reserved keywords in identifier position without quoting, and allows any keyword in identifier position when backtick-quoted.