SQL is parsed incorrectly when `trailing_commas` is not set

When parser not set `trailing_commas=true` in `ParserOptions` or use `BigQueryDialect`, the following SQL will be wrongly parse instead of throw an error.

```sql
SELECT foo, bar, FROM baz

-- Will be wrongly parse instead of throw an error.

SELECT foo, bar, FROM AS baz
```

In theory it should throw a error

relevant code

```rust
#[test]
fn parse_range_select() {
let statements = Parser::parse_sql(&GenericDialect {}, "SELECT foo, bar, FROM baz").unwrap();
println!("{}", statements[0]);
}
```

从 parse_range_select 示例中的 Parser::parse_sql 调用开始，检查 trailing_commas 未设置时 GenericDialect 如何处理 SELECT 列表。添加一个涵盖所示查询的回归测试：拒绝带有尾随逗号的格式错误语法，同时继续支持已配置的 trailing_commas 行为。

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