Accept CREATE SEQUENCE options in any order

[LucaCappelletti94]

CREATE SEQUENCE options were parsed by a fixed chain of independent if blocks, one per option, so only a single order was accepted. CREATE SEQUENCE s INCREMENT BY 1 START WITH 1 parsed, but CREATE SEQUENCE s START WITH 1 INCREMENT BY 1 left the INCREMENT keyword unconsumed and failed with Expected: end of statement. PostgreSQL treats these as an unordered list.

Therefore, following the same pattern we used in other methods, parse_create_sequence_options now loops, dispatching on whichever option keyword comes next and breaking when none matches, and rejects repeated options. Options are recorded in the order written, so Display round-trips the input unchanged.

[codecov-commenter]

Codecov Report

❌ Patch coverage is 84.00000% with 8 lines in your changes missing coverage. Please review.
✅ Project coverage is 80.98%. Comparing base (9ae00e7) to head (4d8634f).

Files with missing lines	Patch %	Lines
src/parser/mod.rs	81.81%	0 Missing and 8 partials ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #2414      +/-   ##
==========================================
+ Coverage   80.96%   80.98%   +0.02%     
==========================================
  Files          42       42              
  Lines       33359    33356       -3     
  Branches    33359    33356       -3     
==========================================
+ Hits        27009    27014       +5     
+ Misses       2790     2788       -2     
+ Partials     3560     3554       -6     

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.