### 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
if (entries.length != columns.length) {
                            throw new IllegalArgumentException(
                                format(
                                    "Error line [{}]: Incorrect number of entries; expected [{}] but found [{}]",
                                    lineNumber,
                                    columns.length,
                                    entries.length
                                )
                            );
                        }
                        for (int i = 0; i < entries.length; i++) {
                            var entry = entries[i];
                            try {
                                columns[i].append(entry);
                            } catch (Exception e) {
                                throw new IllegalArgumentException(
                                    format("Error line [{}]: Cannot parse entry [{}] with value [{}]", lineNumber, i + 1, entry),
                                    e
                                );
                            }
                        }
                    }
                }
                lineNumber++;
            }
        }
        var columnNames = new ArrayList<String>(columns.length);
        var blocks = Arrays.stream(columns)
            .peek(b -> columnNames.add(b.name))
            .map(b -> b.builderWrapper.builder().build())