BUG: When callout is transferred to private space, members of the initial space get error, when try to access the contribution from activity logs

[Comoque1]

Describe the bug
A clear and concise description of what the bug is.

To Reproduce
Steps to reproduce the behavior:

1. Go to dev env
2. Create space 'A'
3. Create a callout or contribution to a callout using space member
4. Create private space 'B'
5. Transfer the callout from space 'A' to space 'B'
6. Using space 'A' member open activity logs of the space
7. Click on the contribution - urlResolver error is thrown

Expected behavior
TBD

Additional context
If the target space is public - user doesn't experience issue.

mutation transferCallout($transferData: TransferCalloutInput!) {
  transferCallout(transferData: $transferData) {
    id
    nameID
    isTemplate
    visibility
  }
}

Areas that will be affected as part of the fix
Optional, to be added by developer if relevant