Fix AnomalyDetectorRestApiIT.testUpdateAnomalyDetectorNameToNew test …

…logic

Previously, the test checked if the new detector and the parsed new detector had different last update times. This was not the intended behavior. The correct check should be between the old and new detector's last update time. This discrepancy was mostly masked by serialization and deserialization differences, but surfaced in JDK 8 on Windows where the timestamps matched.

Changes:
- Updated test to compare old vs. new detector's last update time.

Testing:
- Ran `gradle build`.

Signed-off-by: Kaituo Li <[email protected]>

src/test/java/org/opensearch/ad/rest/AnomalyDetectorRestApiIT.java

@@ -384,11 +384,7 @@ public void testUpdateAnomalyDetectorNameToNew() throws Exception {
         AnomalyDetector resultDetector = getAnomalyDetector(detectorWithNewName.getDetectorId(), client());
         assertEquals("Detector name updating failed", detectorWithNewName.getName(), resultDetector.getName());
         assertEquals("Updated anomaly detector id doesn't match", detectorWithNewName.getDetectorId(), resultDetector.getDetectorId());
-        assertNotEquals(
-            "Anomaly detector last update time not changed",
-            detectorWithNewName.getLastUpdateTime(),
-            resultDetector.getLastUpdateTime()
-        );
+        assertNotEquals("Anomaly detector last update time not changed", detector.getLastUpdateTime(), resultDetector.getLastUpdateTime());
     }
 
     public void testUpdateAnomalyDetectorWithNotExistingIndex() throws Exception {