Fix: force the consistency of location in accompanying period

- internally, the entity remove the addressLocation when the
  personLocation is set, and vice-versa;
- this commit add a migration which may solve the case when both case
  happens (priority to personLocation + keep the history)
- add a constraint on the database to avoid such situation

.changes/unreleased/Fixed-20230629-124412.yaml

@@ -0,0 +1,6 @@
+kind: Fixed
+body: Force the db to have either a person_location or a address_location, and avoid
+  to have both also internally in the entity
+time: 2023-06-29T12:44:12.019663991+02:00
+custom:
+  Issue: ""