update NGs after loading from NVS

[moshe-braner]

from SetupCommon::initSetup() instead of later in SetupMenu::begin() - this moves, for example, init_routing() to SetupNG. And therefore also moved update_routing() from a menu action function to an NG set() action function. This change will allow being more selective in starting WiFi TCP server tasks, based on individual router settings rather than the bitfield variables as a whole. For example, rt_s1_s2 (which has nothing to do with WiFi) should not require starting up both 8881 and 8882 TCP servers. This cannot be done with init_routing() currently in SetupMenu::begin() since it is called after the WiFi TCP server tasks have been started. I also see other uses for this mechanism later, for example, unpacking additional settings bitfields, and handling an overall master_mode variable.

[iltis42]

Current flexibility in WiFi server task startup is okay for almost any usage.
Beside that, the proclaimed startup of 8881 and 8882 TCP servers, are not started both by rt_s1_s2, but from serial1_speed and serial2_speed, see:

XCVario/main/WifiApp.cpp

Line 281 in 0e30066

if( serial2_speed.get() != 0 && serial2_tx.get() != 0 ) // makes only sense if there is data from AUX = serial interface S2

Risk of this change without a concrete benefit for the master branch is too high. Unclear what happens in upgrades from older version. Therefore not taken over.