MLE-12345 Reworking how test plumbing clears a database

The "clear" that happens via DELETE v1/search causes intermittent failures on Jenkins.

Author: rjrudin

marklogic-client-api-functionaltests/src/test/java/com/marklogic/client/functionaltest/ConnectedRESTQA.java

@@ -30,6 +30,7 @@
 import com.marklogic.mgmt.resource.temporal.TemporalAxesManager;
 import com.marklogic.mgmt.resource.temporal.TemporalCollectionLSQTManager;
 import com.marklogic.mgmt.resource.temporal.TemporalCollectionManager;
+import org.slf4j.LoggerFactory;
 
 import javax.net.ssl.*;
 import java.io.IOException;
@@ -317,8 +318,13 @@ public static void deleteDB(String dbName) {
 
 	public static void clearDB(int port) {
 		try (DatabaseClient client = newDatabaseClientBuilder().withPort(port).build()) {
-			QueryManager mgr = client.newQueryManager();
-			mgr.delete(mgr.newDeleteDefinition());
+			// Trying an eval instead of a "DELETE v1/search", which leads to intermittent errors on Jenkins involving
+			// a "clear" operation on a forest failing.
+			String count = client.newServerEval()
+				.xquery("let $uris := for $uri in cts:uris((), (), cts:true-query()) let $_ := xdmp:document-delete($uri) return $uri " +
+					"return fn:count($uris)")
+				.evalAs(String.class);
+			LoggerFactory.getLogger(ConnectedRESTQA.class).info("Cleared database, deleting {} URIs", count);
 		}
 	}