This seems like a fairly obvious oversight with the column.search api.
Knowing the sequence of columns is necessary for a lot of things that
very sensible real-world api clients need to do when working with columns.
Cherry-picked from https://phabricator.wikimedia.org/rPHABebfe30890b52784d222ec4ed36c05462b2a57f92