Avoid double-parenthesis in JpqlQueryBuilder.InPredicate rendering

[cwangg897]

Prevent duplicate parentheses when rendering IN/NOT IN predicates with expressions that already contain parentheses. Added logic to check if predicate string starts and ends with parentheses before wrapping with additional parentheses.

This change improves JPQL query readability by avoiding patterns like "field IN (('value1', 'value2'))" and ensures proper syntax for subqueries and already-parenthesized expressions.

Added comprehensive unit tests to verify the fix handles various scenarios including regular expressions, pre-parenthesized expressions, and subquery expressions.

• You have read the Spring Data contribution guidelines.
• You use the code formatters provided here and have them applied to your changes. Don’t submit any formatting related changes.
• You submit test cases (unit or integration tests) that back your changes.
• You added yourself as author in the headers of the classes you touched. Amend the date range in the Apache license header if needed. For new types, add the license header (copy from another file and set the current year only).

[cwangg897]

I'm not sure if the code formatting has been properly applied.
I'm using IntelliJ IDEA, and I downloaded the eclipse-formatting.xml file from the official repository and applied it using the Eclipse Code Formatter plugin in IntelliJ.
Could you please check if the formatting looks correct?

[mp911de]

There are still more formatting-related changes than those concerning the actual change. Please make sure to reduce or remove all formatting-related changes, otherwise, this PR creates more work for us than addressing the issue ourselves.

[cwangg897]

There are still more formatting-related changes than those concerning the actual change. Please make sure to reduce or remove all formatting-related changes, otherwise, this PR creates more work for us than addressing the issue ourselves.

Yes, I’ve removed it.

[mp911de]

Awesome, thank you.

[mp911de]

Thank you for your contribution. That's merged and polished now. The formatting changes originate from us not applying consistently our formatting style. Additionally, I have simplified the tests slightly.