### 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
assumeTrue("Test " + testName + " is not enabled", isEnabled(testName));
            doTest();
        } catch (Throwable th) {
            throw reworkException(th);
        }
    }
    @Override
    protected final boolean enableWarningsCheck() {
        return false;  // 
    }
    public boolean logResults() {
        return false;
    }
    private void doTest() throws Exception {
        var actualResults = executePlan();
        var expected = loadCsvSpecValues(testCase.expectedResults);
        var log = logResults() ? LOGGER : null;
        assertResults(expected, actualResults, log);
        assertWarnings(actualResults.responseHeaders().getOrDefault("Warning", List.of()));
    }
    protected void assertResults(ExpectedResults expected, ActualResults actual, Logger logger) {
        CsvAssert.assertResults(expected, actual, logger);
        /*
         * Comment the assertion above and enable the next two lines to see the results returned by ES without any assertions being done.
         * This is useful when creating a new test or trying to figure out what are the actual results.
         */
        // 
        // 
    }
    private static IndexResolution loadIndexResolution(String mappingName, String indexName) {