Change default config to not use ITime

Since ClimaCoupler does not support ITime, we do not enable ITime as the
default configuration. As such, we select a few configs to use ITime to
ensure that ITime works as intended.

config/default_configs/default_config.yml

@@ -349,4 +349,4 @@ use_itime:
   help: "If set to true, ITime (integer time) is used. This should be set to true when precision with time is necessary as floating point time may encounter floating point errors. When converting an ITime back to a float, the float will be Float64. See the examples below where there will be a difference in ITime and Float64:
   1. Surface conditions that explicitly depend on time (e.g. LifeCycleTan2018, TRMM_LBA, etc.),
   2. Time dependent forcing/tendencies use time rounded to the nearest unit of time for dt"
-  value: true
+  value: false

config/model_configs/box_density_current_test.yml

@@ -17,4 +17,5 @@ dt_save_state_to_disk: "5secs"
 netcdf_interpolation_num_points: [40, 40, 80]
 diagnostics:
   - short_name: [wa, ua, va, ta, thetaa, ha]
-    period: 5secs 
+    period: 5secs
+use_itime: true

config/model_configs/diagnostic_edmfx_aquaplanet_gpu.yml

@@ -20,3 +20,4 @@ precip_model: 0M
 dt: 120secs
 t_end: 12hours
 toml: [toml/diagnostic_edmfx_0M.toml]
+use_itime: true

config/model_configs/prognostic_edmfx_aquaplanet.yml

@@ -30,3 +30,4 @@ diagnostics:
   - short_name: [arup, waup, taup, thetaaup, haup, husup, hurup, clwup, cliup, waen, tke, lmix]
     reduction_time: average
     period: 1hours
+use_itime: true

config/model_configs/sphere_baroclinic_wave_equilmoist_conservation_ft64.yml

@@ -9,3 +9,4 @@ diagnostics:
   - short_name: [massa, energya]
     period: 1days
     writer: dict
+use_itime: true