Query IP of wifi module

[LnnrtS]

This adds a separate logical channel in the serial interface to communicate with the wifi module itself (not with connected clients). For now the wifi module answers all messages on that channel with a 4 bytes indicating its ipv4 address (or 0.0.0.0 if not connected).

This information still needs to be made available to the UI

[danngreen]

Working on this now. It displays the IP or "not connected" if M4 reports none.

It would be nice to also somehow distinguish between "No wifi module" vs. "No wifi signal". Because if the UART connection to the Wifi module were to become disrupted, getCurrentIP() continues to report the last good IP it had.

Maybe we need a separate interface like bool WifiInterface::is_connected(). The interface would need to keep track of when M4 sent a request for the IP, and if didn't hear back in some timeout period, then the state is Disconnected. This could be a separate issue/PR, too, but the data would end up displaying on the same GUI page and we could use the same inter-core comm channel

[LnnrtS]

This now distinguishes between no response of the request and not connected to the network. After everything is up and running I can connect/disconnect the wifi module or turn off/on the access point and it shows the correct state in the gui.

The only thing that is missing is that the wifi module hangs on startup until it gets connected to a network. But this is will show as no module connected. So I need to make the connection attempt a separate async task.

Also the the gui could be refined (should probably show "no expanders" again when the wifi module gets disconnected)

[LnnrtS]

This will profit from #294

[danngreen]

Cool. It works on firmware, but compilation fails for the simulator because std::expected is not supported:
https://github.com/4ms/metamodule/actions/runs/9861851753

We could upgrade the minimum version of clang/gcc required I suppose? Or roll our own std::expected

[LnnrtS]

The simulator build still needs to be set to c++23 (also with a recent compiler) but yes, ubuntu 22.04's gcc doesn't have that feature. I see that 24.04 is available in beta (but not yet set to latest). So just changing to ubuntu-24.04 in the github actions file should do that.

Since this project is still going to run for some time I would say it makes sense to make gcc12 (and CXX_STANDARD 23) a requirement going forward. Nore sure if how this would affect other developers at the moment though..

[danngreen]

Clang 16 and Apple Clang 15 support std::expected. Our README states that clang 14 or later is required. It already requires gcc 12 or later, so that should be fine. But for anyone using clang 14, 15, or Apple Clang 14 would need to update.

I think is the direction to go, but I don't want to shock any other devs. Let me ask around...

[LnnrtS]

Ok. I have this prepared in #298

[LnnrtS]

The only thing that is missing is that the wifi module hangs on startup until it gets connected to a network. But this is will show as no module connected. So I need to make the connection attempt a separate async task.

This is working now

[LnnrtS]

Closed in favor of #309