Edge case of merge members with similar activities resulting 500 error

[epipav]

Changes proposed ✍️

• When merging two members, if a member has two activities from the same platform with the same timestamp, the Lodash unique function was also removing the second activity from the merged member, causing an activity without a member on MemberRepository.setActivities function call, resulting in a 500 error.
• Now we're checking the activity uniqueness using the activity.sourceId field

Checklist ✅

• Label appropriately with Feature, Enhancement, or Bug.
• Tests are passing.
• New backend functionality has been unit-tested.
• Environment variables have been updated:
  • Local frontend configuration: frontend/.env.dist.local, frontend/.env.dist.composed.
  • Local backend: backend/.env.dist.local, backend/.env.dist.composed.
  • Configuration docs have been updated.
  • Team members only: update environment variables in override, staging and production env. files and trigger update config script.
• API documentation has been updated (if necessary) (see docs on API documentation).
• Quality standards are met.
• All changes have been tested in a staging site.
• All changes are working locally running crowd.dev's Docker local environment.

[joanreyero]

LGTM!