It's useful in certain automated workflows to make sure we recurse in
directories whose name conflicts with files in other revisions.

In addition it makes it possible to avoid building a potentially costly regex,
improving performance when the set of files to match explicitly is large.

The benchmark below are run in the following configuration :
 # data-env-vars.name             = mozilla-central-2018-08-01-zstd-sparse-revlog
 # benchmark.name                 = files
 # benchmark.variants.rev         = tip
 # benchmark.variants.files       = all-list-filepath-sorted
 # bin-env-vars.hg.flavor         = no-rust

It also includes timings using the re2 engine (through the `google-re2` module)
to show how much can be saved by just using a better regexp engine.


Pattern                time (seconds)        time using re2
-----------------------------------------------------------
just "."                0.4                    0.4
list of "filepath:…"    1.3                    1.3
list of "path:…"       25.7                    3.9
list of patterns       29.7                   10.4

As you can see, Without re2, using "filepath:" instead of "path:" is a huge
win. With re2, it is still about three times faster to not have to build the
regex.