Increase statement_timeout and lock_timeout in db migration

[GianlucaFicarelli]

Considering acceptable a statement timeout of 30 seconds, it should fix the failure in the current db migration:

sqlalchemy.exc.OperationalError: (psycopg2.errors.QueryCanceled) canceling statement due to statement timeout

during the query:

UPDATE measurement_kind
SET measurement_label_id = ml.id
FROM measurement_label ml
WHERE ml.entity_type = 'cell_morphology'::entitytype
AND ml.pref_label = measurement_kind.pref_label

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.

Flag	Coverage Δ
pytest	97.60% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

🚀 New features to boost your workflow:

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

[GianlucaFicarelli]

For the record, when running the migration locally with a similar db and ~400k records, without private data:

2026-01-05 12:31:29.685 UTC [7218] LOG:  statement:
	            UPDATE measurement_kind
	            SET measurement_label_id = ml.id
	            FROM measurement_label ml
	            WHERE ml.entity_type = 'cell_morphology'::entitytype
	            AND ml.pref_label = measurement_kind.pref_label
	       
2026-01-05 12:31:33.470 UTC [7218] LOG:  duration: 3785.887 ms

and for comparison, even doing an update without join takes more than 2 seconds:

entitycore=*# UPDATE measurement_kind set measurement_label_id=measurement_label_id;
UPDATE 397461
Time: 2291.946 ms (00:02.292)