UtilitiesTest JUnit can fail from time to time

[johnbrvc]

Describe the issue:
A git CI build failed on UtilitiesTest.testgetDateTime().

To Reproduce:
Extremely difficult to reproduce (see below).

Expected behavior:
The UtilitiesTest.testgetDateTime() should always succeed.

Actual behavior:
The UtilitiesTest.testgetDateTime() can fail since the time can change between the initial Utilities.getDateTime() and the new Date() on the next line in UtilitiesTest.java. Basically, the test is obtaining a formatted time string (Utilities.DATE_TIME_FORMAT_STRING = "yyyyddMMhhmmss.SSS") from two different sources and comparing the non-millisecond part (first 15 characters), It is still possible (but extremely unlikely) that the first time string was obtained at, say, 20251502141310.999 and the next one was at 20251502141311.000. Notice that the first 15 characters, 20251502141310. and 20251502141311. will compare differently causing the JUnit test to fail, and consequently, the CI Build process to fail.

Environment:
All, but the Git CI in this case.

Log Info:

    [junit] Testsuite: edu.csus.ecs.pc2.core.UtilitiesTest
    [junit] Tests run: 29, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.347 sec
    [junit] 
    [junit] ------------- Standard Output ---------------
    [junit] Load from file /__w/pc2v9/pc2v9/samps/contests/mini/config/groups.tsv
    [junit] Load from file /__w/pc2v9/pc2v9/samps/contests/mini/config/teams.tsv
    [junit] Added 151 accounts and 12 groups.
    [junit] Load from file /__w/pc2v9/pc2v9/samps/contests/mini/config/groups.tsv
    [junit] Load from file /__w/pc2v9/pc2v9/samps/contests/mini/config/teams.tsv
    [junit] Added 151 accounts and 12 groups.
    [junit] ------------- ---------------- ---------------
    [junit] Testcase: testgetDateTime(edu.csus.ecs.pc2.core.UtilitiesTest):	FAILED
    [junit] First part of string should match 
    [junit] junit.framework.AssertionFailedError: First part of string should match 
    [junit] 	at edu.csus.ecs.pc2.core.UtilitiesTest.testgetDateTime(UtilitiesTest.java:119)
    [junit] 
    [junit] 
    [junit] Test edu.csus.ecs.pc2.core.UtilitiesTest FAILED

Screenshots:

Additional context:
Apparently the author thought about the fact that comparing the milliseconds could fail (a comment in the code: // may not match actual milliseconds.) However, no consideration was given to the fact that seconds may roll over as well (and consequently minutes, hours, etc.)

I'm not exactly sure of the best way to fix this, other than just removing the test, or, perhaps if it fails, sleep 10ms and try again?