Nested type modifiers/complex type

Example Trino SQL:
```sql
SELECT
row_id,
array_agg(
CAST(
ROW(
total_amount
)
AS
ROW(
total_amount Decimal(14,2)
)
)
ORDER BY payment_requested_date DESC
) AS payment_request_details
FROM
iceberg.my_table_name
GROUP BY 1
```

This throws an error when using `GenericDialect`, specifically when it tries to parse `Decimal(14,2)`: ```ParserError("Expected: type modifiers, found: ( at Line: 10, Column: 37")```

Stepping through the code it looks like this is because it does not support deeply nested definitions because `parse_optional_type_modifiers` does not allow `Token::LParen`.

This may be by design, but it may break parsing when you get to really complex queries (e.g. deeply nested rows).

Comienza por el manejo de GenericDialect de las definiciones de tipos anidados y parse_optional_type_modifiers; después, reproduce la consulta proporcionada para confirmar el fallo de Decimal(14,2). Traza cómo se analizan los tipos ROW anidados y añade cobertura de regresión que demuestre que la consulta se analiza correctamente con sus modificadores de tipo anidados.

Escrito por el modelo de indexación a partir del texto del issue.