Dynamic package resolution with unresolvable or fragment package exports can lead to invalid wirings

With the latest code in trunk calling org.apache.felix.resolver.ResolverImpl.resolve(ResolveContext, Resource, Requirement, List<Capability>) with a List<Capability> containing a Capability from a fragment will lead to an invalid Wire.

This looks similar to FELIX-4897 and appears to be a regression.

There are two types of failures.
1) Where the fragment has a valid host to resolve against. In this case I would expect the Wire.getProvider() to be the host revision for the fragment, but the current code returns the fragment revision

2) Where the fragment has no valid host available. In this case I would expect no Wire to be returned in the result from the ResolverImpl.resolve call.