Use identifiable structs for AST variant fields

When consuming the generated AST for further processing, one needs to match against and deconstruct `ast::Statement` instances. Currently, the fields of this enum's variants are defined inline... which makes it impossible for downstream code to represent the nested structures as types. For example, consider this structure:

https://github.com/ballista-compute/sqlparser-rs/blob/35ef0eee3857c59827b2587bc813218a00dce264/src/ast/mod.rs#L490-L497

I propose we migrate to the following pattern.
```rust
pub struct AnalyzeStatement {
table_name: ObjectName,
partitions: Option>,
for_columns: bool,
....
}
pub enum Statement {
Analyze(AnalyzeStatement),
...
}
```

Obviously this is a massive breaking change, but that seems OK given the `0.9.x` crates.io version.

Thoughts?

Comece revisando o enum Statement e as definições relacionadas em src/ast/mod.rs, especialmente as linhas vinculadas em torno de 490-497. Avalie como cada campo inline de uma variante poderia se tornar uma struct identificável, preservando a forma proposta do AST. Considera-se concluído quando as variantes relevantes do AST usam structs nomeadas e a alteração incompatível da API resultante é aplicada de forma consistente.

Escrita pelo modelo de indexação a partir do texto da issue.