### Description

As discussed in https://github.com/elastic/elasticsearch/issues/98995, queries will not have an implicit order - as such the CSV spec framework would have to account for this.
As some tests will want to check the order while others might not, it's best to have a flag or marker when the out of order occurs and use a different assertion method.
x-pack/plugin/esql/src/test/java/org/elasticsearch/xpack/esql/CsvTests.java
}
    private Throwable reworkException(Throwable th) {
        StackTraceElement[] stackTrace = th.getStackTrace();
        StackTraceElement[] redone = new StackTraceElement[stackTrace.length + 1];
        System.arraycopy(stackTrace, 0, redone, 1, stackTrace.length);
        redone[0] = new StackTraceElement(getClass().getName(), groupName + "." + testName, fileName, lineNumber);
        th.setStackTrace(redone);
        return th;
    }
    // 
    private static void opportunisticallyAssertPlanSerialization(PhysicalPlan... plans) {
        for (var plan : plans) {
            var tmp = plan;
            do {
                if (tmp instanceof LocalSourceExec) {
                    return; // 
                }
            } while (tmp.children().isEmpty() == false && (tmp = tmp.children().get(0)) != null);
            SerializationTestUtils.assertSerialization(plan);
        }
    }
    private void assertWarnings(List<String> warnings) {
        List<String> normalized = new ArrayList<>(warnings.size());
        for (String w : warnings) {
            normalized.add(HeaderWarning.extractWarningValueFromWarningHeader(w, false));
        }
        assertMap(normalized, matchesList(testCase.expectedWarnings));
    }
}