[FIX] util/records: avoid row-based IS NOT NULL

While using row-based `IS {,NOT} NULL`, especially after doing
LEFT JOIN we need to be very carefull as:
1. IS NULL = true if the `row is NULL OR all columns are NULL`[^1]
2. IS NOT NULL = true if the `row is NOT NULL AND all columns are NOT
   NULL`[^1]

So for making it safe, we used `t2.<column> IS NOT NULL` instead
of `t2 IS NOT NULL` when the <column> was used while joining

ref: odoo/upgrade#8957

[^1]: https://www.postgresql.org/docs/12/functions-comparison.html

closes #361

Signed-off-by: Christophe Simonis (chs) <[email protected]>

Author: jepbarasgarov

src/util/records.py

@@ -1744,11 +1744,12 @@ def replace_record_references_batch(
                          -- there is no target already present within the same constraint
                         NOT EXISTS(SELECT 1 FROM {table} WHERE {res_model_whr} AND {jmap_expr} AND {where_clause})
                          -- there is no other entry with the same target within the same constraint
-                        AND NOT (t2 IS NOT NULL AND {where_clause2})
+                        AND NOT (t2.{res_id} IS NOT NULL AND {where_clause2})
                         """,
                         table=ir.table,
                         res_model_whr=res_model_whr,
                         jmap_expr=jmap_expr,
+                        res_id=ir.res_id,
                         where_clause=SQLStr(" AND ".join(format_query(cr, "{0}=t.{0}", col) for col in uniq_cols))
                         if uniq_cols
                         else SQLStr("True"),