Fix "any" matching when not all globs match

[jalaziz]

The previous logic had a bug where the "any" pattern list could match
against changed files even when not all globs matched a single changed
file. The bug arose individual globs in the "any" list were tested
against all changed files individually. Therefore, as long as at least
one changed file matched an individual glob in the list, a successful
match would be found.

The correct behavior is to match all the globs in the list against each
individual file. This ensures that is possible to define exlcusions
correctly and matched the documented behavior.

[jalaziz]

@dakale Still testing this, but discovered a bug in the previous logic.

There was an edge case where "any" matching would be successful when separate files each individually matched a glob in the "any" list. However, this can already be accomplished by listing out each glob on its own line.

The correct behavior should be matching all the globs against each changed file and returning true when at least one match is found.

The "all" logic was updated to match the testing order, but it should be functionally equivalent.

[jalaziz]

Ran some tests against a test repo I have and I believe this logic works and fixed the issue.

[siemelnaranhighfive]

LGTM but the comment on old line 4220 "// equivalent to "Array.some()" but expanded for debugging and clarity" is gone.

[jalaziz]

@dakale Just wanted to ping on this since master is currently buggy.

[dakale]

Sorry for slow response, just saw this. LGTM

[jalaziz]

Thanks!