Increase SingleFeatureTest coverage to insure all dependencies in pom.xml file

SingleFeatureTests currently can give false positives if:

a) Your feature depends on a bundle that is built in your local repo
b) Your features/pom.xml does not contain a dependency for that bundle.

Example:

example/foo/pom.xml
example/features/pom.xml
example/features/src/main/features/features.xml

If your features.xml contains a feature:

<feature bar>
<bundle>foo</bundle>
</features>

and you don't have a dependency for foo in features/pom.xml, then if you build
example/ (as happens on merge and verify) then SingleFeatureTests will succeed, because karaf will be able to find the foo bundle in ~/.m2 because you built it, but downstream projects (like integration) will not get foo pulled into their ~/.m2 and will fail.

We need to think up a way to also catch this case.