Allow setting the recursion limit for sql parsing

[cetra3]

Which issue does this PR close?

No issue, just running into this in production.

Rationale for this change

At the moment there isn't a clean way to set the recursion limit on the sql parser.

What changes are included in this PR?

This PR allows a config option, datafusion.sql_parser.recursion_limit which allows overriding the recursion limit.

Are these changes tested?

No, it's just a config option.

Are there any user-facing changes?

There will be some changes to public facing API. I'm also not sure if this is the best approach here, as DFParser might need a deeper refactor to keep things clean.

[jatin510]

I see that a recursion limit of 50 is introduced for SQL parsing.
Is this based on specific performance benchmarks or potential stack overflow risks?
Also, is there any reference to similar constraints in databases like PostgreSQL, or is this a DataFusion-specific safeguard?

@cetra3

[cetra3]

@jatin510 This number is actually the default in sqlparser: https://github.com/apache/datafusion-sqlparser-rs/blob/b482562618caa3efa89c2f42f87472b00a270926/src/parser/mod.rs#L187

So it will essentially be the exact same behaviour, but configurable.

[adriangb]

I'll note that we encountered this when parsing a dynamically generated expression containing a lot of ANDs and ORs. I believe these sorts of expressions are parsed recursively, so it's pretty easy to hit 50 levels of recursion if each AND is a level.