Ivy matcher picks up committed sbt resolution-cache under target/

The maven/ivy manifest matcher in bibliothecary accepts files like:

```
target/scala-2.11/resolution-cache/reports/org.scala-sbt.temp-...-runtime.xml
spark-1.3.0/assembly/target/resolution-cache/reports/org.apache.spark-spark-assembly_2.10-plugin.xml
```

These are sbt/ivy build artifacts (per-configuration resolution reports), not source manifests. They show up when a repo has committed its `target/` directory. Excluding paths containing `/target/` and `/resolution-cache/` from the ivy match would drop the noise.

The change is in `ecosyste-ms/bibliothecary`; filing here since that fork has issues disabled.

Start by locating the maven/ivy manifest matcher in bibliothecary and any tests covering ivy paths. Check the supplied target/ and resolution-cache/ examples, then run the relevant matcher tests. Done means those build-artifact paths no longer match while genuine ivy manifests still do.

Written by the indexing model from the issue text.