feat(conversations): Follow up for event conversation handling

[miaulalala]

☑️ Resolves

• Fix 📅 Handling of event conversations - ⚙️ API - Follow up #14689

🛠️ API Checklist

🚧 Tasks

• ...

🏁 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

[SystemKeeper]

Tested and works fine for me. Test cases:

• Past event
• Ongoing event
• Future event
• Future future event (start > 16h from now)
• Editing of title and description and sync to talk
• Manually copying an existing event room link to another event -> converted to regular room

From the code/test-side nickvergessen should take a look, can't fully judge.

One thing I noticed: Editing title and description is not prevent on API level for event rooms - should we do that?

[miaulalala]

One thing I noticed: Editing title and description is not prevent on API level for event rooms - should we do that?

Added a 403 for editiing room name and description for event rooms.

[nickvergessen]

/backport to stable31

[backportbot]

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

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

# Create the new backport branch
git checkout -b backport/14713/stable31

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

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

Error: Failed to check for changes with origin/stable31: No changes found in backport branch

---

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