Fix flaky test_timeout_set_correctly on PyPy/Windows

Relax assertAlmostEqual tolerance from 2 decimal places (0.005) to 1
(0.05) in timeout tests. The _export_batch refactoring adds a
serialization step between deadline calculation and the HTTP POST,
consuming a few extra milliseconds that exceed the tight tolerance on
slow runtimes like PyPy on Windows.

Author: Krishnachaitanyakc

exporter/opentelemetry-exporter-otlp-proto-http/tests/test_proto_log_exporter.py

@@ -525,7 +525,7 @@ def test_timeout_set_correctly(self, mock_post):
 
         def export_side_effect(*args, **kwargs):
             # Timeout should be set to something slightly less than 400 milliseconds depending on how much time has passed.
-            self.assertAlmostEqual(0.4, kwargs["timeout"], 2)
+            self.assertAlmostEqual(0.4, kwargs["timeout"], 1)
             return resp
 
         mock_post.side_effect = export_side_effect

exporter/opentelemetry-exporter-otlp-proto-http/tests/test_proto_span_exporter.py

@@ -345,7 +345,7 @@ def test_timeout_set_correctly(self, mock_post):
 
         def export_side_effect(*args, **kwargs):
             # Timeout should be set to something slightly less than 400 milliseconds depending on how much time has passed.
-            self.assertAlmostEqual(0.4, kwargs["timeout"], 2)
+            self.assertAlmostEqual(0.4, kwargs["timeout"], 1)
             return resp
 
         mock_post.side_effect = export_side_effect