- 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
