logging::test::test_config_file failure on Windows bot

This was observed on a PR check run. The test passed on a subsequent rerun.

failures:

---- logging::test::test_config_file stdout ----
config "file": Ok(File { level: Warn, path: "C:\\Users\\RUNNER~1\\AppData\\Local\\Temp\\dropshot-af77ac2c25c9d09a.exe.2092.file_dir\\log.out", if_exists: Fail })
note: configured to log to "C:\Users\RUNNER~1\AppData\Local\Temp\dropshot-af77ac2c25c9d09a.exe.2092.file_dir\log.out"
config "file": Ok(File { level: Warn, path: "C:\\Users\\RUNNER~1\\AppData\\Local\\Temp\\dropshot-af77ac2c25c9d09a.exe.2092.file_dir\\log.out", if_exists: Append })
note: configured to log to "C:\Users\RUNNER~1\AppData\Local\Temp\dropshot-af77ac2c25c9d09a.exe.2092.file_dir\log.out"
config "file": Ok(File { level: Trace, path: "C:\\Users\\RUNNER~1\\AppData\\Local\\Temp\\dropshot-af77ac2c25c9d09a.exe.2092.file_dir\\log.out", if_exists: Truncate })
note: configured to log to "C:\Users\RUNNER~1\AppData\Local\Temp\dropshot-af77ac2c25c9d09a.exe.2092.file_dir\log.out"
thread 'logging::test::test_config_file' panicked at 'assertion failed: should_be_before.timestamp() <= time_after.timestamp()', dropshot\src\test_util.rs:786:13


failures:
    logging::test::test_config_file

Start with logging::test::test_config_file and the failure assertion in dropshot/src/test_util.rs:786, using the linked Windows PR check as the reproduction context. Compare the failing run with the subsequent successful rerun and determine why the timestamp ordering assertion is intermittent. Done means the test no longer fails spuriously on the Windows bot.