warp_esp32_i2c, warp_esp32_rtc: Reduce I2C timeout durations

I2C accesses are performed blocking and in case of a missing response,
the main task is blocked for the full timeout duration.
I2C responses are either very quick or missing completely,
so there's no point in using long timeout durations.
Reduce the timeouts to sensible minimums, to avoid blocking
the main task for too long when either I2C chip stops responding.

The temperature sensor replies usually take less than 1ms, sometimes up to 3ms, so use 6ms to be safe.
The RTC replies usually take about 0.5ms, sometimes up to 2ms, so use 4ms to be safe.

software/src/modules/warp_esp32_i2c/warp_esp32_i2c.cpp

@@ -31,7 +31,7 @@
 #pragma GCC diagnostic push
 #pragma GCC diagnostic ignored "-Wold-style-cast"
 // portTICK_PERIOD_MS expands to an old style cast.
-static TickType_t i2c_timeout = 1000 / portTICK_PERIOD_MS;
+static TickType_t i2c_timeout = 6 / portTICK_PERIOD_MS;
 #pragma GCC diagnostic pop
 
 static uint8_t tmp_cmd_buf[I2C_LINK_RECOMMENDED_SIZE(2)] = {};

software/src/modules/warp_esp32_rtc/warp_esp32_rtc.cpp

@@ -34,7 +34,7 @@
 #pragma GCC diagnostic push
 #pragma GCC diagnostic ignored "-Wold-style-cast"
 // portTICK_PERIOD_MS expands to an old style cast.
-static TickType_t i2c_timeout = 1000 / portTICK_PERIOD_MS;
+static TickType_t i2c_timeout = 4 / portTICK_PERIOD_MS;
 #pragma GCC diagnostic pop
 
 static uint8_t intToBCD(uint8_t num) {