SNOW-1357844: fix flaky test caused by oob telemetry datetime comparsion

[sfc-gh-aling]

Please answer these questions before submitting your pull requests. Thanks!

1. What GitHub issue is this PR addressing? Make sure that there is an accompanying issue to your PR.

   Fixes SNOW-1357844

2. Fill out the following pre-review checklist:

   • I am adding a new automated test(s) to verify correctness of my new code
   • I am adding new logging messages
   • I am adding a new telemetry message
   • I am adding new credentials
   • I am adding a new dependency

3. Please describe how your code solves the related issue.

pytest.approx only supports number, datetime is not supported, so previously implementation doesn't work at all.
change to use timestamp to the approx equal

[sfc-gh-mvashishtha]

@sfc-gh-aling could you please pip install pytest-repeat pytest-xdist and run the test 1000 times before and after this change (I think parallelism with -n 32 might help speed it up) to check that the flakiness goes away?

[sfc-gh-aling]

@sfc-gh-mvashishtha I changed to use mock, we shall be good now. thanks for the suggestion

command pytest tests/mock_unit/test_oob_telemetry.py::test_unit_oob_log_not_implemented_error --count 1000 -n 32 passes

[sfc-gh-mvashishtha]

@sfc-gh-aling one more nit

command pytest tests/mock_unit/test_oob_telemetry.py::test_unit_oob_log_not_implemented_error --count 1000 -n 32 passes

Thanks for checking, but it seems to pass on the main branch as well, so it doesn't reproduce the flake. That's okay. I think mocking the time should work.

[sfc-gh-mvashishtha]

LGTM! thanks