fix(Postgres): escape apostrophes in JSON path segments

[roxblnfk]

🔍 What was changed

• Postgres JSON path segments are now escaped: apostrophes inside a key are doubled before the segment is wrapped into an SQL string literal.
• Affects every Postgres JSON condition: whereJson, whereJsonContains, whereJsonDoesntContain, whereJsonContainsKey, whereJsonDoesntContainKey, whereJsonLength and their or* variants.

Why?

A key with an apostrophe (e.g. data->it's) broke the generated SQL on Postgres, while the other drivers already escape it.

Checklist

• How was this tested:
  • Functional tests added
  • Postgres driver suite run locally against Postgres from tests/docker-compose.yml

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 95.66%. Comparing base (166c6ea) to head (56ce86f).

Additional details and impacted files

@@            Coverage Diff            @@
##                2.x     #271   +/-   ##
=========================================
  Coverage     95.66%   95.66%           
  Complexity     2230     2230           
=========================================
  Files           142      142           
  Lines          6341     6341           
=========================================
  Hits           6066     6066           
  Misses          275      275           

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.