.NET: Thin client: Advanced exception handling

IGNITE-6250 introduced basic exception propagation: success code and a message.

We should add full message details to the protocol:

• Exception message
• Class
• Stack trace
• Native exception binary object (if any): for example, when exception occured in C++ or .NET callback

To avoid exposing sensitive information in production environmanets, introduce a configuration property to exclude exception details (like many web servers have, e.g. <customErrors mode="Off" /> in ASP.NET)

Dev list discussion:
http://apache-ignite-developers.2346864.n4.nabble.com/Exception-handling-in-thin-client-should-we-pass-stack-traces-to-the-client-td22392.html