feat(reply_private): Enhance reply private quote

[existentialcoder]

☑️ Resolves

• Fix Reply privately does not quote message #6301

🖌️ UI Checklist

• Handle privatereply by passing the parentToken for a new message send and schedule

🖼️ Screenshots / Screencasts

https://streamable.com/9e1rzv

🏁 Checklist

• 🌏 Tested with different browsers / clients:
  • Chromium (Chrome / Edge / Opera / Brave)
  • Firefox
  • Safari
  • Talk Desktop
  • Integrations with Files sidebar and other apps
  • Not risky to browser differences / client
• 🖌️ Design was reviewed, approved or inspired by the design team
• ⛑️ Tests are included or not possible
• 📗 User documentation in https://github.com/nextcloud/documentation/tree/master/user_manual/talk has been updated or is not required

---

🛠️ API Checklist

🚧 Tasks

• Introduce replyToToken on sendMessage and scheduleMessage on ChatController
• Create a message with special verb private_reply to store all the parent details

🏁 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

[github-actions]

Hello there,
Thank you so much for taking the time and effort to create a pull request to our Nextcloud project.

We hope that the review process is going smooth and is helpful for you. We want to ensure your pull request is reviewed to your satisfaction. If you have a moment, our community management team would very much appreciate your feedback on your experience with this PR review process.

Your feedback is valuable to us as we continuously strive to improve our community developer experience. Please take a moment to complete our short survey by clicking on the following link: https://cloud.nextcloud.com/apps/forms/s/i9Ago4EQRZ7TWxjfmeEpPkf6

Thank you for contributing to Nextcloud and we hope to hear from you soon!

(If you believe you should not receive this message, you can add yourself to the blocklist.)

[Antreesy]

Please split your changes into at least three commits for readability:

• PHP changes
• regenerated openapi files (json ans ts)
• Frontend changes

[existentialcoder]

Please split your changes into at least three commits for readability:

• PHP changes
• regenerated openapi files (json ans ts)
• Frontend changes

Have done this. Kindly re-review and let me know if all your existing comments are addressed and test cases work.

[nickvergessen]

Some small comments, but mostly fine backend-wise.

Would be good to have integration tests, but can also do that in a follow up

[existentialcoder]

Some small comments, but mostly fine backend-wise.

Would be good to have integration tests, but can also do that in a follow up

I would like to take this as a follow-up as this PR got already big enough. Addressed all the comments, otherwise :)

[Antreesy]

I really like the feature, but it should have a good ground to continue maintain and build from (e.g. we can use the same approach later to forward messages). At the moment I'm not fond of constructing the message object on client side, esp. if it breaks older and mobile clients

[existentialcoder]

I really like the feature, but it should have a good ground to continue maintain and build from (e.g. we can use the same approach later to forward messages). At the moment I'm not fond of constructing the message object on client side, esp. if it breaks older and mobile clients

Have made all UI changes on top of @nickvergessen 's API change. Let me know if this is good to go now @Antreesy

[Antreesy]

Mostly minor comments from frontend side. Otherwise works fine, even render on old clients seems acceptable to me (visible text, non-working link is ok)

Regarding visual - we can discuss with designers and take over a follow-up after merge. I think we shouldn't show the full message, 2-3 lines can be enough

[Antreesy]

Last iteration, I hope. Noticed a couple of things to pay attention to and revert leftovers from previous chages, otherwise that's a green light from me =)

[existentialcoder]

Last iteration, I hope. Noticed a couple of things to pay attention to and revert leftovers from previous chages, otherwise that's a green light from me =)

This is done

[nickvergessen]

• Failing tests are fixed by tests: Use guests config to not hash the user id #17567