[MarioPym]

Summary

When a federated share is received, the "You received a new remote share … from …" activity is published without a link, so clicking it in the activity stream does nothing. The other remote share activities of the same provider (accepted, declined) already set a link.

This adds a link to the Files view where the user can find the share:

• Pending shares (/apps/files/pendingshares) when the share waits to be accepted.
• Shared with you (/apps/files/sharingin) when it is auto-accepted from a trusted server.

The link is set for user shares and for every member of a group share. The auto-accept condition is now computed once and reused in both branches.

How to test

1. Share a file or folder from a remote server with a local user (federated share).
2. As the recipient, open the Activity app, or call GET /ocs/v2.php/apps/activity/api/v2/activity/all:
   • Before: the "You received a new remote share" entry has an empty link and is not clickable.
   • After: link is https://your-server/index.php/apps/files/pendingshares and opens the Pending shares view.
3. With "Automatically accept shares from trusted federated servers" enabled and the remote added as a trusted server, the link points to /apps/files/sharingin.

Unit tests: apps/federatedfilesharing/tests/OCM/CloudFederationProviderFilesTest.php (pending user share, group share with one event per member, auto-accepted share).

Checklist

• Code is properly formatted
• Sign-off message is added to all commits
• Tests (unit, integration, api and/or acceptance) are included
• Screenshots before/after for front-end changes
• Documentation (manuals or wiki) has been updated or is not required
• Backports requested where applicable (ex: critical bugfixes)
• Labels added where applicable (ex: bug/enhancement, 3. to review, feature component)
• Milestone added for target branch/version (ex: 32.x for stable32)

AI (if applicable)

• The content of this PR was partly or fully generated using AI