Fixes the #silenced? method when "only" patterns are present

As soon as a path is matched against an "only" regexp, it's
not silenced, so it's silenced if it doesn't match any "only"
regexps.

If fixes the previous logic that was requiring a path to match
all "only" patterns in order to not be silenced, meaning that
it was silenced as soon as it didn't match an "only" regexp
(even if it matched another "only" regexp).

I think with this logic, the `only` option works well, ~~no need for
`only_dirs` / `only_exts`, you can do it with regexps, .e.g.:~~

Edit: because of some adapters's and the current implementation, it's possible that a first check for silenced paths is done against directories only which would return `true` (i.e. "silenced") even if the `only` pattern defines an extension that would match a modified file *inside* the false-positive-silenced directory.

**You can ignore the rest of this comment**

```ruby
only: [%r{^foo/}, /\.rb$/]
```

will match (with `Dir.pwd` being `/Users/remy/project`:

* `/Users/remy/project/foo/bar.txt` (`foo/` folder)
* `/Users/remy/project/bar.rb` (`.rb` extension)
* `/Users/remy/project/bar/foo.rb` (`.rb` extension)

will not match:

* `/Users/remy/project/bar/foo.txt` (no `foo/` folder, no `.rb` extension)
* `/Users/remy/project/bar.txt` (no `foo/` folder, no `.rb` extension)