In the translation code for DocumentSourceMatch, we translate the match expression. Then, if the resulting ABT has a top-level composition, we flatten it into a chain of separate FilterNodes. In the find path, we don't do this second flattening step. This seems problematic. We probably want the ABTs for match expressions generated by the find path and agg path to be consistent.