Fix WSL container event timestamps - #41717

Network event test does not verify nanosecond timestamp precision

test/​windows/​WSLCTests.cpp:7518

This positive-value check does not verify the network timestamp change: it also passes if a callback forwards Docker's seconds-valued time, or if the stored value loses its fractional nanoseconds. The container lifecycle test compares each stored timeNano with Docker's TimeNano; please make the same comparison for at least one network event (matched by network and action) so a network-only precision regression fails this test.

Prevent nanosecond overflow when applying UTC offsets

src/​windows/​common/​timestamp.cpp:322

time uses signed 64-bit nanoseconds, so adding a local UTC offset here can overflow even when timeNano itself is valid (for example, a time near the upper limit with a +14:00 offset). The CLI can then print a date centuries earlier. Apply the offset to whole seconds and format the nine fractional digits separately; cover both timestamp limits in the formatter tests.

Use timed cancellation when reading events

test/​windows/​WSLCTests.cpp:7410

ReadEvents passes a null cancellation handle to GetNext. If any of these five events is missing or skipped, the stream waits until its year-3000 until bound instead of failing the test. Keep that far-future bound to test the comparison, but pass a short, timed cancellation handle to each read and fail if it expires.

Historical sub-minute offsets produce incorrect timestamp suffix

src/​windows/​common/​timestamp.cpp:330

Historical time zones can have offsets with seconds (for example, +00:19:32). Here the clock is shifted by the full offset, but the suffix at line 330 prints only minutes, so the timestamp describes a different instant. Shift the clock by the same whole-minute offset printed in the suffix, and use Z if that offset becomes zero. Add a test for a sub-minute offset.