Allowed use of & operator at top level of CorpusQL queries.

Example: [lemma="man"] & [word="men"] wasn't valid before, but is now.
It means the same thing as [lemma="man" & word="men"]. The or (|)
operator at this level was already valid.
Made sure files are always indexed in the same order.