Start using activityRelations instead of activities for syncMember and syncOrganization

[joanagmaia]

Currently, we get data from QuestDb to get activities information to trigger syncMember and syncOrganization which are then responsible to calculate aggregates.
However, we are currently facing issues running syncMember because activities might not yet be updated in QuestDb, resulting in syncMember runing on outdated data.

We could instead use activityRelations to get all data required by syncMember and syncOrganization which could be more performant and guarantee that the relations would be up to date when the syncs were triggered.