fix(migrations): use double question-mark (#19557)

Use double question mark to escape parametrization by jdbi.
https://jdbc.postgresql.org/documentation/query/#using-the-statement-or-preparedstatement-interface

(cherry picked from commit 76c9b5a)

bootstrap/sql/migrations/native/1.6.3/postgres/schemaChanges.sql

@@ -1,5 +1,5 @@
 -- Add constraint to apps_data_store
 ALTER TABLE apps_data_store ADD CONSTRAINT entity_relationship_pky PRIMARY KEY (identifier, type);
-UPDATE user_entity SET json = jsonb_set(json::jsonb, '{isBot}', 'false'::jsonb, true) WHERE NOT (json ? 'isBot');
+UPDATE user_entity SET json = jsonb_set(json::jsonb, '{isBot}', 'false'::jsonb, true) WHERE NOT (json ?? 'isBot');
 ALTER TABLE user_entity ADD COLUMN isBot BOOLEAN GENERATED ALWAYS AS ((json ->> 'deleted')::boolean) STORED NOT NULL;
 CREATE INDEX idx_isBot ON user_entity (isBot);