fix(files): fix unshare action and merge duplicate shares

[skjnldsv]

Fix unshare action

The delete action now properly adjust itself depending on the selectcion

• Delete
• Unshare
• Delete and unshare if shares and files are mixed in the selection

cc @nextcloud/designers for wording validation

Fix #14437

Merge duplicates shares in the views

The sharing views will group the same nodes coming from the same source ⚠️
This can happen if a user share a folder with different groups and you're a member of them. The same file will appear multiple times in the Shared with you section.
We ONLY MERGE entries with the same location on the user file system, which means, if you have two different shares but they are in different folders (moved) and therefore are matching different shares, we will NOT group them, and their actions will both target different shares.

cc @nextcloud/designers for wording validation and icon choice

[skjnldsv]

Found a bug in https://github.com/nextcloud-libraries/nextcloud-files, nextcloud-libraries/nextcloud-files#862

[nimishavijay]

Delete and unshare if shares and files are mixed in the selection

Would all the files be deleted? or would the not-shared files be deleted and shared files be unshared? I'm wondering if it makes sense to just show Delete and Unshare as 2 separate actions if the files are mixed. ccing @jancborchardt because he was involved in the issue :)

Merge duplicates shares in the views
Shared multiple times with different users

We are moving away from "users" in the wording. So Shared multiple times with different people or Shared multiple times with different accounts (no strong preference there, if I had to pick I'd go with "people")

[skjnldsv]

I'm wondering if it makes sense to just show Delete and Unshare as 2 separate actions if the files are mixed.

Technically not possible. We do not show actions if they only target a specific subset of the selection. Considering a selection with share and owned-files, it would shown neither options as none of the two actions can be executed on the current selection

We are moving away from "users" in the wording. So Shared multiple times with different people or Shared multiple times with different accounts (no strong preference there, if I had to pick I'd go with "people")

Done :)

[szaimen]

LGTM from design perspective but didnt test

[skjnldsv]

Failure not related