Losing error information on constructor open() call

[lauri-piikivi]

Description

Issue for UDP and TCP Socket on different technologies and stack implementations
Not based on compile and run, reviewing code manually.

The socket constructor hides the open calls from returning errors underneath, and thus different implementations may fail -- see for example open on
https://github.com/ARMmbed/esp8266-driver/blob/master/ESP8266Interface.cpp

Note that this may impact cloud client, as they do not explicitly call open, only the constructor and connect.

Issue request type

[] Question
[ ] Enhancement 
[X ] Bug 

mbed-os/features/netsocket/UDPSocket.h

Line 50 in 949cb49

open(stack);

[adbridge]

Internal Jira reference: https://jira.arm.com/browse/ONME-3928

[SeppoTakalo]

Fixed in:

• Deprecate TCP/UDPSocket open-calling constructors #8794
• Socket constructors which call open are deprecated mbed-os-5-docs#838