### 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
BOOLEAN(Booleans::parseBoolean, Boolean.class);
        private static final Map<String, Type> LOOKUP = new HashMap<>();
        static {
            for (Type value : Type.values()) {
                LOOKUP.put(value.name(), value);
            }
            
            LOOKUP.put("SHORT", INTEGER);
            LOOKUP.put("BYTE", INTEGER);
            
            LOOKUP.put("I", INTEGER);
            LOOKUP.put("L", LONG);
            LOOKUP.put("UL", UNSIGNED_LONG);
            LOOKUP.put("D", DOUBLE);
            LOOKUP.put("K", KEYWORD);
            LOOKUP.put("S", KEYWORD);
            LOOKUP.put("STRING", KEYWORD);
            LOOKUP.put("TXT", TEXT);
            LOOKUP.put("N", NULL);
            LOOKUP.put("DATE", DATETIME);
            LOOKUP.put("DT", DATETIME);
            LOOKUP.put("V", VERSION);
        }
        private final Function<String, Object> converter;
        private final Class<?> clazz;
        Type(Function<String, Object> converter, Class<?> clazz) {
            this.converter = converter;
            this.clazz = clazz;
        }
        public static Type asType(String name) {