### 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
return LOOKUP.get(name.toUpperCase(Locale.ROOT));
        }
        public static Type asType(ElementType elementType) {
            return switch (elementType) {
                case INT -> INTEGER;
                case LONG -> LONG;
                case DOUBLE -> DOUBLE;
                case NULL -> NULL;
                case BYTES_REF -> KEYWORD;
                case BOOLEAN -> BOOLEAN;
                case DOC -> throw new IllegalArgumentException("can't assert on doc blocks");
                case UNKNOWN -> throw new IllegalArgumentException("Unknown block types cannot be handled");
            };
        }
        Object convert(String value) {
            if (value == null) {
                return null;
            }
            return converter.apply(value);
        }
        Class<?> clazz() {
            return clazz;
        }
    }
    record ActualResults(
        List<String> columnNames,
        List<Type> columnTypes,
        List<String> dataTypes,
        List<Page> pages,
        Map<String, List<String>> responseHeaders