### 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
logMetaData(actualNames, actualTypes, logger);
        }
        var expectedNames = expected.columnNames();
        var expectedTypes = expected.columnTypes();
        assertThat(
            format(
                null,
                "Different number of columns returned; expected [{}] but actual was [{}]",
                expectedNames.size(),
                actualNames.size()
            ),
            actualNames,
            Matchers.hasSize(expectedNames.size())
        );
        
        
        
        for (int column = 0; column < expectedNames.size(); column++) {
            String expectedName = expectedNames.get(column);
            String actualName = actualNames.get(column);
            if (expectedName.equals(actualName) == false) {
                
                String expectedSet = expectedName;
                String actualSet = actualName;
                if (column > 1) {
                    expectedSet = expectedNames.get(column - 1) + "," + expectedName;
                    actualSet = actualNames.get(column - 1) + "," + actualName;
                }
                assertEquals("Different column name [" + column + "]", expectedSet, actualSet);
            }