### 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
mvValue = new StringBuilder();
                    previousMvValue = entry.substring(1);
                    mvValue.append(previousMvValue);
                }
            } else if (entry.endsWith("]")) {
                if (previousMvValue == null) {
                    throw new IllegalArgumentException(
                        format(
                            "Error line [{}:{}]: Unexpected end of a multi-value field value (no previous starting point); found [{}]",
                            lineNumber,
                            pos,
                            entry
                        )
                    );
                }
                mvValue.append("," + entry.substring(0, entry.length() - 1));
                mvCompressedEntries.add(mvValue.toString());
                mvValue = null;
                previousMvValue = null;
            } else {
                if (mvValue != null) {
                    if (entry.length() == 0) {
                        throw new IllegalArgumentException(
                            format(
                                "Error line [{}:{}]: Unexpected missing value in a multi-value column; found [{}]",
                                lineNumber,
                                pos,
                                csvLine.substring(pos - 1)
                            )
                        );