make `Parser` generic around dialect

if we care about performance, we should stop using dynamic dispatch and make the parser generic around the dialect, with that we could make lots of these methods `const` (or drop the `Precedence` enum and just have const values on the trait) and probably improve performance significantly in general.

That would of course be a big change to the public API.

This is definitely how would implement `Parser` if I was starting now, but I think we should see some evidence that parsing SQL is a meaningful chunk of time for anyone before making a change like this.

My guess is that:
* even for quick queries, SQL parsing is <1% of query time
* making `Parser` generic and therefore dropping the restriction on `Dialect` that it has to be 'object safe' would actually only save us ~20%

If both those assumptions are right, this doesn't seem worth it unless it makes the code generally easier to reason with and work on.

_Originally posted by @samuelcolvin in https://github.com/sqlparser-rs/sqlparser-rs/issues/1379#issuecomment-2289164242_

(separate issue seems worth it for this discussion)

首先检查 Parser、Dialect 和 Precedence enum，然后确定 SQL 解析是否占据查询时间中有意义的一部分。对当前的动态分派方式进行基准测试，并将其与通用 Parser 设计进行比较。当获得关于性能收益的证据，并确定公共 API 变更的方向后，即可视为完成。

由索引模型根据 Issue 内容生成。