### 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/CsvAssert.java
expectedName,
                        column,
                        pageIndex,
                        expectedType,
                        blockType
                    ),
                    expectedType,
                    blockType
                );
            }
        }
    }
    static void assertData(ExpectedResults expected, ActualResults actual, Logger logger) {
        assertData(expected, actual.values(), logger, Function.identity());
    }
    public static void assertData(
        ExpectedResults expected,
        Iterator<Iterator<Object>> actualValuesIterator,
        Logger logger,
        Function<Object, Object> valueTransformer
    ) {
        assertData(expected, EsqlTestUtils.getValuesList(actualValuesIterator), logger, valueTransformer);
    }
    public static void assertData(
        ExpectedResults expected,
        List<List<Object>> actualValues,
        Logger logger,
        Function<Object, Object> valueTransformer
    ) {
        var expectedValues = expected.values();