Allows to disable sanity socket check, by default enabled.
While allocating underlying socket descriptors, at the connection creation using (socket system call) vortex_connection_new, it could happen that the OS assign a socket descriptor used for standard task like: stdout(0), stdin(1), stderr(2).
This happens when the user app issue a close() call over the previous standard descriptors (0,1,2) causing vortex to allocate a reserved descriptor with some funny behaviors.
Starting from previous context, any user app call issuing a console print will cause to automatically send to the remote site the message printed, bypassing all vortex mechanisms.
Obviously, this is an odd situation and it is not desirable. By default, Vortex Library includes a sanity check to just reject creating a Vortex Connection with an underlying socket descriptor which could cause applications problems.
You can disable this sanity check using this function.