Use a float for the tolerance in the timer tests

When using an `int`, we need to do a double conversion, first to `float`
and then back to `int`, and due to rounding errors, this means there are
inconsistencies between the expected and actual values.

Using `float` directly ensures we are comparing the same values in the
tests and in the code.

Signed-off-by: Leandro Lucarella <[email protected]>

Author: llucax

tests/test_timer.py

@@ -132,20 +132,31 @@ def test_policy_skip_missed_and_resync_examples() -> None:
 
 
 @hypothesis.given(
-    tolerance=st.integers(min_value=_min_timedelta_microseconds, max_value=-1)
+    tolerance=st.floats(
+        min_value=timedelta.min.total_seconds(),
+        max_value=-1,
+        exclude_max=False,
+        allow_nan=False,
+        allow_infinity=False,
+    ),
 )
-def test_policy_skip_missed_and_drift_invalid_tolerance(tolerance: int) -> None:
+def test_policy_skip_missed_and_drift_invalid_tolerance(tolerance: float) -> None:
     """Test the SkipMissedAndDrift policy raises an error for invalid tolerances."""
     with pytest.raises(ValueError, match="delay_tolerance must be positive"):
         SkipMissedAndDrift(delay_tolerance=timedelta(microseconds=tolerance))
 
 
 @hypothesis.given(
-    tolerance=st.integers(min_value=0, max_value=_max_timedelta_microseconds),
+    tolerance=st.floats(
+        min_value=0,
+        max_value=timedelta.max.total_seconds(),
+        allow_nan=False,
+        allow_infinity=False,
+    ),
     **_calculate_next_tick_time_args,
 )
 def test_policy_skip_missed_and_drift(
-    tolerance: int, now: int, scheduled_tick_time: int, interval: int
+    tolerance: float, now: int, scheduled_tick_time: int, interval: int
 ) -> None:
     """Test the SkipMissedAndDrift policy."""
     hypothesis.assume(now >= scheduled_tick_time)