Fix UI being unresponsive for up to 30seconds in really rare edge cases

This must have made it in while testing something out & forgetting to remove it, don't set the timeout to 10 seconds - with the default of 3 retransmissions (and each retransmission waits for timeout seconds) it can block the UI for up to 30seconds on operations that don't use async to update params (pretty much all).

Author: Consti10

app/telemetry/settings/mavlinksettingsmodel.cpp

@@ -359,7 +359,7 @@ bool MavlinkSettingsModel::try_fetch_all_parameters()
         }
         qDebug()<<"Done removing old params";
         // now fetch all params using mavsdk (this talks to the OHD system(s).
-        param_client->set_timeout(10);
+        //param_client->set_timeout(10);
         const auto params=param_client->get_all_params(true);
         for(const auto& int_param:params.int_params){
             MavlinkSettingsModel::SettingData data{QString(int_param.name.c_str()),int_param.value};