Upgrade to sqlparser 0.61.0

[alamb]

DRAFT until SQL parser is released

Which issue does this PR close?

• part of Release sqlparser-rs version 0.61.0 around 2026-02-01 datafusion-sqlparser-rs#2117

Rationale for this change

Keep up to date with dependencies

I think @Samyak2 specifically would like access to the : field syntax

What changes are included in this PR?

1. Update to 0.61.0
2. Update APIs

Are these changes tested?

Yes by existing tests

Are there any user-facing changes?

New dependency

[alamb]

There are a few sqllogictest errors like this

External error: 35 errors in file /Users/andrewlamb/Software/datafusion2/datafusion/sqllogictest/test_files/map.slt

1. statement failed: DataFusion error: SQL error: ParserError("Expected: ), found: { at Line: 3, Column: 8")
[SQL] CREATE TABLE map_array_table_1
AS VALUES
  (MAP {1: [1, NULL, 3], 2: [4, NULL, 6], 3: [7, 8, 9]}, 1, 1.0, '1'),
  (MAP {4: [1, NULL, 3], 5: [4, NULL, 6], 6: [7, 8, 9]}, 5, 5.0, '5'),
  (MAP {7: [1, NULL, 3], 8: [9, NULL, 6], 9: [7, 8, 9]}, 4, 4.0, '4')
;
at /Users/andrewlamb/Software/datafusion2/datafusion/sqllogictest/test_files/map.slt:18

[alamb]

I had Codex make up a DataFusion specific dialect to get the tests passing. I now need to clean it up, Occam's razor style

[Samyak2]

Should we perhaps consider the errors as bugs in GenericDialect instead? There's some SQL that was previously parsed successfully by GenericDialect but fails now -- sounds like something to fix

[Samyak2]

I have an issue and a PR for this upstream: apache/datafusion-sqlparser-rs#2204 and apache/datafusion-sqlparser-rs#2205

Seems to fix all the 35 errors here

[alamb]

Should we perhaps consider the errors as bugs in GenericDialect instead? There's some SQL that was previously parsed successfully by GenericDialect but fails now -- sounds like something to fix

Yes, likely -- this is great news -- thank you @Samyak2

[alamb]

This is a drive by cleanup -- no need to return and ? -- just return is fine

[alamb]

Should we perhaps consider the errors as bugs in GenericDialect instead? There's some SQL that was previously parsed successfully by GenericDialect but fails now -- sounds like something to fix

Yes, likely -- this is great news -- thank you @Samyak2

Thanks again @Samyak2 -- I updated this branch to include the fix (and the 0.61.0 Release candidate) and all the tests pass now.

Thanks 🙏 !