feat(chat): Expose the "top most parent" ID as thread ID

[nickvergessen]

☑️ Resolves

• Fix API - Message threads #9679

🚧 Tasks

• Add threading system
  • Expose top most parent id as thread id
• Define capability
• Adjust documentation

🏁 Checklist

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

[Antreesy]

Able to receive from web client, message by default gets threadId=0, 1-st level replies get the same threadId as parent param, deep replies inherit threadId of the original first message

Note: at the moment thread messages would look messy in the original message list. Also in order to show threads, we need to receive all messages by threadId, including the original one (by id), and also all the original thread messages (which have thread started - maybe, additional param?)

[nickvergessen]

at the moment thread messages would look messy in the original message list.

As per last team week we will only add an option to filter for a thread, we will not restructure the messages list into a thread list making it very easy to miss messages.

Also in order to show threads, we need to receive all messages by threadId, including the original one (by id), and also all the original thread messages (which have thread started - maybe, additional param?)

Thought about this too, but we just filter the existing message list, so the existing API should work in most cases?