Issues with substituted exports with require bundle

When resolving require-bundle requirements there is an issue if the bundle being required has substituted exports. The issue is that any requiring bundle will not have the export substituted included in their own class space. At runtime the OSGi core specification requires that substituted exports be accessible to requiring bundles. This can cause issues in the consistency check done by the resolver because the class space the requiring bundle will be missing packages that should be visible.

The resolver needs to keep track of substituted exports and make sure to include any substitutions in the class spaces of the requiring bundles.