One often reported issue is that the ESPEasy node (especially ESP8266 ones) will crash when WiFi is unstable.
This could be due to memory suddenly filling up by the controller queue.
When creating a new item for the controller queue, there was no `(std::nothrow)` included on the `new` calls, so if running out of memory this might have thrown a `std::bad_alloc` exception, which are not caught and thus ESPEasy might crash on it.
This also fixes a timeout issue on ESP32 as the WiFiClient timeout is set in seconds (!!!!!)
See: https://github.com/espressif/arduino-esp32/pull/6676
Extremely frustrating design choice as it has taken extreme amounts of time to debug those issues!