Remove mesh_sds_timeout_secs and bump node_db_lite to 100 for now

meshtastic/config.proto

@@ -306,15 +306,6 @@ message Config {
      */
     uint32 wait_bluetooth_secs = 4;
 
-    /*
-     * Deprecated in 2.1.X
-     * Mesh Super Deep Sleep Timeout Seconds
-     * While in Light Sleep if this value is exceeded we will lower into super deep sleep
-     * for sds_secs (default 1 year) or a button press
-     * 0 for default of two hours, MAXUINT for disabled
-     */
-    uint32 mesh_sds_timeout_secs = 5 [deprecated = true];
-
     /*
      * Super Deep Sleep Seconds
      * While in Light Sleep if mesh_sds_timeout_secs is exceeded we will lower into super deep sleep
@@ -869,4 +860,4 @@ message Config {
     LoRaConfig lora = 6;
     BluetoothConfig bluetooth = 7;
   }
-}
+}

meshtastic/deviceonly.options

@@ -2,7 +2,7 @@
 # https://jpa.kapsi.fi/nanopb/docs/reference.html#proto-file-options
 
 # FIXME pick a higher number someday? or do dynamic alloc in nanopb?
-*DeviceState.node_db_lite max_count:80
+*DeviceState.node_db_lite max_count:100
 
 # FIXME - max_count is actually 32 but we save/load this as one long string of preencoded MeshPacket bytes - not a big array in RAM
 *DeviceState.receive_queue max_count:1