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]);
}
```

Start with the Parser::parse_sql call in the parse_range_select example and inspect how GenericDialect handles SELECT lists when trailing_commas is unset. Add a regression test covering the shown queries, with malformed trailing-comma syntax rejected while the configured trailing_commas behavior remains supported.

Written by the indexing model from the issue text.