base: don't check unicity when migrating Person.reference to user_id

This activity is spawned on all nodes, which cause too many conflicts.
We can take the risk here, assuming that references were already OK
before migration.
2 jobs for fix/setId_serialize
in 0 seconds, using 0 compute credits, and was queued for 0 seconds