Component fails to confirm - Linking Issue for Feather ESP32V2 causing "ERROR: Please define a network interface!"

[tyeth]

Found during display testing of the E-ink featherwing (a magtag screen with 3buttons).
Component didn't confirm after add, due to the network issue.

[display] Successfully initialized epd display!␍␊
[display] Display added or replaced successfully!␍␊
ERROR: Please define a network interface!␍␊
Establishing network connection...␍␊
Performing a WiFi scan for SSID...ERROR: Please define a network interface!␍␊
ERROR [WDT RESET IN 25]: ␍␊
ERROR: Unable to find WiFi network, rebooting soon...␍␊

Digging a bit deeper it looks like we end up with two different versions of the WS global. This might be down to an older version of gcc for the esp32 versus esp32s3/s2 etc where the link-time-optimisiation is better and correctly hooks the Wippersnapper_WiFi overloads of the Wippersnapper base class.

Switching the global to be of type Wippersnapper_WiFi resolves the linking issue, but does require a small refactor. The user should see no difference, and we just have a minor tweak to each cpp file using WS.

Associated draft PR for testing - #829

These changes solve the issue for display confirm and runNetFSM from displays/controller.cpp
7857c9d...3d601a9