Switch to psycopg 3

Part the First of https://redmine.teklia.com/issues/10050

• All psycopg2 imports are renamed to psycopg, fortunately the modules did not move.
• psycopg2.extras.execute_values does not exist anymore, so I had to make the cursed has_children SQL on element lists even more cursed than before.
• psycopg does not support tuples as parameters for a IN %s construct, so I also had to make the ListDatasetElements neighbors SQL even more cursed.
• The syntax for arrays changed from ARRAY['a', 'b', 'c'] to '{a,b,c}'::text[]. It used to be the {} syntax a while ago, then something changed it to ARRAY[] (maybe Django 5, I forgot), and brackets are back.
• UUIDs are now serialized without dashes, to save four characters, so I had to update basically every assertExactQueries call.

Base image build: https://gitlab.teklia.com/arkindex/backend/-/jobs/707340

changed milestone to %Arkindex 1.7.3

requested review from @babadie

assigned to @erouchet

mentioned in merge request !2520 (merged)

added 4 commits

• dec4e774 - 1 commit from branch release-1.7.3
• 5b1d0c42 - Switch to psycopg 3
• 045ff854 - Add comments on the even more cursed SQL
• b5bb1832 - New base image

Compare with previous version

I updated my existing setup on python3.10, removed manually psycopg2-binary, and was able to:

• arkindex runserver
• apply a few DB migrations
• use the API endpoints through frontend
• use the backend admin

The placeholders hack are strange but I do not have abetter idea

enabled an automatic merge when all merge checks for b5bb1832 pass

merged

mentioned in merge request !1535 (closed)