### 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/qa/testFixtures/src/main/java/org/elasticsearch/xpack/esql/CsvTestUtils.java
) {
        Iterator<Iterator<Object>> values() {
            return EsqlQueryResponse.pagesToValues(dataTypes(), pages);
        }
    }
    static void logMetaData(List<String> actualColumnNames, List<Type> actualColumnTypes, Logger logger) {
        
        StringBuilder sb = new StringBuilder();
        StringBuilder column = new StringBuilder();
        for (int i = 0; i < actualColumnNames.size(); i++) {
            if (i > 0) {
                sb.append(" | ");
            }
            column.setLength(0);
            column.append(actualColumnNames.get(i));
            column.append("(");
            column.append(actualColumnTypes.get(i));
            column.append(")");
            sb.append(trimOrPad(column));
        }
        int l = sb.length();
        logger.info(sb.toString());
        sb.setLength(0);
        sb.append("-".repeat(Math.max(0, l)));
        logger.info(sb.toString());
    }
    static void logData(List<List<Object>> values, Logger logger) {
        for (List<Object> list : values) {
            logger.info(rowAsString(list));
        }