es_wifi: fix start client connection for UDP sockets

[joelguittet]

This pull-request fixes an issue with the ES_WIFI_StartClientConnection function when using UDP socket: commands P3 and P4 (respectively to set remote IP address and port) must be executed not only for TCP/SSL connection. Indeed, while trying to open an UDP socket, we have to set the UDP server address and port!!

Reference documentation from Inventek at https://www.inventeksys.com/iwin/wp-content/uploads/IWIN_Command_Set_Users_Manual.pdf does not limit executing P3 and P4 commands to TCP/SSL.

Implementation from getting-started example from Azure RTOS also made this modification. See https://github.com/eclipse-threadx/getting-started/blob/37ff82f757070f3fa5364acb1ac06fcc7a5b9d38/STMicroelectronics/B-L475E-IOT01A/lib/netx_driver/inventek/es_wifi.c#L1635.

[RJMSTM]

ST Internal Reference: 188471