All technical sites will be down for several hours for technical works

Hello everybody :) currently I am slowly working on 29.0.0 with new API implementation and API designers accepted as successful solution to add direct_messages_topic_id which is 100% identical to message_thread_id but related to direct messages topics.

For now I faced strange but important choice:

* To put both message_thread_id and direct_messages_topic_id in send requests without modifying external API (which you are using in this library). There will be some probability that they will add topics in topics (topics in channels direct messages for each user) and it will require to make breaking changes. But for now it looks like some ugly and strange decision if they will make it
* Add separated directMessagesTopicId to be able to set it separately with messageThreadId (usually named as threadId). In that case it will be two different types which in fact are identical, but in code they will be partially-incompatible