Disable/hide share edit options when user can not edit the share

[provokateurin]

Summary

We were still showing the user the options to edit and delete the share, but they will face an unhelpful error message when they try to continue.

Before:

After:

We could also hide the quick edit button, but I think it's nice to leave it there to still indicate the permission of the share, even if the current user can not change them.

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)

[provokateurin]

/backport to stable30

[provokateurin]

/backport to stable29

[provokateurin]

/backport to stable28

[provokateurin]

/backport to stable27

[nfebe]

LGTM

[provokateurin]

/compile

[backportbot]

The backport to stable27 failed. Please do this backport manually.

# Switch to the target branch and update it
git checkout stable27
git pull origin stable27

# Create the new backport branch
git checkout -b backport/49747/stable27

# Cherry pick the change from the commit sha1 of the change against the default branch
# This might cause conflicts, resolve them
git cherry-pick 1e44c671 f2898df2 3a640929

# Push the cherry pick commit to the remote repository and open a pull request
git push origin backport/49747/stable27

Error: No changes found in backport branch

---

Learn more about backports at https://docs.nextcloud.com/server/stable/go.php?to=developer-backports.

[skjnldsv]

/backport to stable30

[skjnldsv]

/backport to stable28

[backportbot]

The backport to stable30 failed. Please do this backport manually.

# Switch to the target branch and update it
git checkout stable30
git pull origin stable30

# Create the new backport branch
git checkout -b backport/49747/stable30

# Cherry pick the change from the commit sha1 of the change against the default branch
# This might cause conflicts, resolve them
git cherry-pick 1e44c671 f2898df2 3a640929

# Push the cherry pick commit to the remote repository and open a pull request
git push origin backport/49747/stable30

Error: Failed to create pull request: Validation Failed: {"resource":"PullRequest","code":"custom","message":"A pull request already exists for nextcloud:backport/49747/stable30."}

---

Learn more about backports at https://docs.nextcloud.com/server/stable/go.php?to=developer-backports.

[backportbot]

The backport to stable28 failed. Please do this backport manually.

# Switch to the target branch and update it
git checkout stable28
git pull origin stable28

# Create the new backport branch
git checkout -b backport/49747/stable28

# Cherry pick the change from the commit sha1 of the change against the default branch
# This might cause conflicts, resolve them
git cherry-pick 1e44c671 f2898df2 3a640929

# Push the cherry pick commit to the remote repository and open a pull request
git push origin backport/49747/stable28

Error: Failed to create pull request: Validation Failed: {"resource":"PullRequest","code":"custom","message":"A pull request already exists for nextcloud:backport/49747/stable28."}

---

Learn more about backports at https://docs.nextcloud.com/server/stable/go.php?to=developer-backports.