fix(Om): fix updateCollection/set() when string contains SQL operators

[Ibochkarev]

Fix updateCollection/set() when string value contains SQL operator keywords (e.g. IN, LIKE)

Previously, xPDOQuery::set() used isConditionalClause() to detect raw SQL expressions. String values containing SQL keywords like "IN", "LIKE", "BETWEEN", or "=" were incorrectly treated as raw SQL and not quoted, causing malformed queries and potential SQL injection.

Changes:

• Remove isConditionalClause check in set() — string fields are now always treated as PARAM_STR and properly quoted
• Simplify duplicate condition: replace redundant elseif (in_array(...)) with else
• Add null type handling in driver-specific construct() for robustness
• Add test cases: LIKE, BETWEEN, =, empty string, apostrophe (O'Brien)
• Add descriptive names to providerUpdateCollection data sets for clearer failure messages

Security: Proper quoting via quote() reduces SQL injection risk. isConditionalClause remains used in where() and other places where SQL expressions are expected.

Fixes #54

[opengeek]

@Ibochkarev — thanks for digging into this and putting together a fix with test cases. The work you did helped bring attention to and sharpen our understanding of the problem.

This PR is being closed because the issue was patched through PR #280, which fixed the set() quoting bug and also introduced xPDOExpression as a formal way to pass raw SQL expressions through the query layer. The approaches overlap significantly, and #280 was the path we took to resolve it.

Your contribution was not wasted. Surfacing this issue and exploring the solution helped greatly. Thank you again.