fix(chat): Allow to edit messages of bots in one-to-one conversations

[nickvergessen]

🛠️ API Checklist

🏁 Checklist

• ⛑️ Tests (unit and/or integration) are included or not possible
• 📘 API documentation in docs/ has been updated or is not required
• 🔖 Capability is added or not needed

[nickvergessen]

Do we need a capability and explicit documentation, or should we just assume it is a bug fix and if editing fails because the client was already updated but the server not, we don't care?

[nickvergessen]

/backport to stable31

[nickvergessen]

/backport to stable30

[nickvergessen]

/backport to stable29

[SystemKeeper]

Do we need a capability and explicit documentation, or should we just assume it is a bug fix and if editing fails because the client was already updated but the server not, we don't care?

We need to change it on client side as well:

https://github.com/nextcloud/talk-ios/blob/fc5a9ebda821f257dddc73ec7169fcbc9f544571/NextcloudTalk/NCChatMessage.swift#L80-L83

But I would say we just enable it server-side and don't care if it wasn't updated.

[Antreesy]

Do we need a capability and explicit documentation

'edit-messages' should be enough, if we backport it to 29?

[backportbot]

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

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

# Create the new backport branch
git checkout -b backport/14344/stable29

# Cherry pick the change from the commit sha1 of the change against the default branch
# This might cause conflicts, resolve them
git cherry-pick a3e3f28e

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

Error: No changes found in backport branch

---

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