Implement TLS 1.3

[Roy2player]

• 1) Protocol abstractions: data, handler;
• 2) Approach to integration with server. As the TLS contains payload for another protocols, server unpacks it before handling. That is a good question where to transfer decision point. It seems to be logically to move it inside server's recv processing function, as the access to TLS data is too specific requirement. I want to save ability to inspect protocol messages.

[Roy2player]

Recently implemented recv buffer provides clear way to communicate with income data, that is perfectly proven by its broad usage. I decided to keep that abstraction. Then, the TLS should be handled in one level deeper, that will be new Connection abstraction, which will separate connection-related responsibilities clearer, then it is implemented for now. In addition, my new thread and error safe approaches will be used in it.

[Roy2player]

Want to highlight here, that one of my main rules is "Then less number of data and functional abstractions, then better" and this additional ones are huge logical parts, which are required to keep code follow the existed MSAPI Philosophy #23