Added the ShareUpdate activity in the space context.

[2403905]

Description

Related Issue

• Fixes <issue_link>

Motivation and Context

How Has This Been Tested?

• test environment:
• test case 1:
• test case 2:
• ...

Screenshots (if appropriate):

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)
• Technical debt
• Tests only (no source changes)

Checklist:

• Code changes
• Unit tests added
• Acceptance tests added
• Documentation ticket raised:

[2403905]

@tboerger The few questions about the activity templates
When a user updates the permission and expiration the ocis emit a single event.
Then the activity uses the template for this event like MessageShareUpdated = l10n.Template("{user} updated {field} for the {resource}")

1. Can we join the fields enum by comma? permission and expiration => permission, expiration
2. We translate the activity message template on the server side. Should we also translate the field data that represents as updated field ( permission, expiration) in this case?

Now:
| admin updated expiration, permissions for the New folder |
translated as
| admin оновив expiration, permissions для the New folder |

Could be:
| admin updated expiration, permissions for the New folder |
translated as
| admin оновив термін дії, дозволи для the New folder |

[tbsbdr]

@2403905 1,2:yes 🙂

[sonarcloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
3.1% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarCloud

[micbar]

who mentioned @tboerger here?