Feat: optionally wrap connectors when using builders

[georgesittas]

Closes #4367
Closes #4362

Now this works:

>>> import sqlglot
>>> import sqlglot.expressions as expressions
>>> from sqlglot.expressions import column
>>>
>>> is_equal_list = ['a'] * 500
>>> is_equal = expressions.false()
>>>
>>>
>>> for value in is_equal_list:
...     is_equal = is_equal.or_(column("a_column").eq(value), wrap=False)
...
>>> is_equal.sql()[:100]
"FALSE OR a_column = 'a' OR a_column = 'a' OR a_column = 'a' OR a_column = 'a' OR a_column = 'a' OR a"

I didn't add a timing test because they're flaky. I think we should refactor the existing ones at some point too.

[VaggelisD]

RE: Iterative generation logic

Could we solve this issue by unwrapping exp.Paren during iteration instead of traversing downwards? This could solve both issues at once, unless the API addition here is nice to have anyways.

[georgesittas]

RE: Iterative generation logic

Could we solve this issue by unwrapping exp.Paren during iteration instead of traversing downwards? This could solve both issues at once, unless the API addition here is nice to have anyways.

Sure, wanna take a stab at it? I think conditionally wrapping in the API makes sense, but improving Generator.binary is also a good idea.

[VaggelisD]

Sure, wanna take a stab at it? I think conditionally wrapping in the API makes sense, but improving Generator.binary is also a good idea.

Sounds good, but since wrap is a QOL more than a "forced" solution we can merge this PR and I'll toy with it later to see what'd be the scope of the changes (if they prove to be worth it)