[Vertica] fix gaps for some datatypes, complex alias support, fix group by for DDL

[PolitePp]

Brief summary of the change made

fixes #5687

1. fix float with precision
2. fix aliasing indentations
3. support aliasing for several columns in some functions
4. support array[data_type] syntax
5. allow over and within group in the same window function
6. fix interval datatype
7. fix numeric data types (no space between a type and a bracket)
8. fix group by in partition by clause for create table command

Are there any other side effects of this change that we should be aware of?

No

Pull Request checklist

• Please confirm you have completed any of the necessary steps below.

• Included test cases to demonstrate any code changes, which may be one or more of the following:

  • .yml rule test cases in test/fixtures/rules/std_rule_cases.
  • .sql/.yml parser test cases in test/fixtures/dialects (note YML files can be auto generated with tox -e generate-fixture-yml).
  • Full autofix test cases in test/fixtures/linter/autofix.
  • Other.

• Added appropriate documentation for the change.

• Created GitHub issues for any relevant followup/future enhancements if appropriate.

[github-actions]

Coverage Results ✅

Name    Stmts   Miss  Cover   Missing
-------------------------------------
TOTAL   17356      0   100%

225 files skipped due to complete coverage.

[coveralls]

coverage: 99.984%. remained the same
when pulling b715fe1 on PolitePp:issue-5687
into b2a4eab on sqlfluff:main.

[WittierDinosaur]

This seems like a regression?

[PolitePp]

Yes, that's true, but if you try to use row datatype not inside array it will fail because it's not implemented, so it seems better to have more specific array support and later add a row datatype

Current changes in the array segment allow me to parse sections with Jinja like:

select
    array[
    {% for metric_event in funnel_events %}
        {% for window_size in window_sizes %}
            null,
        {% endfor %}
    {% endfor %}
    null
]::array[varchar] as agg_data
from tab;

Without new changes, it will violate rule RF06 Missing quoted keyword identifier varchar

[alanmcruickshank]

Looks sensible. Thanks for checking into the potential regression, but on balance it seems reasonable for now.