Resolve a bundle dependency to an existing installation

[carolynvs]

When the bundle dependency graph is resolved, we should also include installations in the same namespace or the global namespace.

The rules for matching an installation are different than matching a new bundle to install because we don't need to run the bundle in order to reuse it. We still need to consider if upgrade/uninstall impacts the constraints put on the bundle interface however. So that needs to be updated in the PEP before implementing this.

• Required outputs must be present. If the parent bundle expects the dependency to produce a mysql connection string, the installation should have that output.
• Bundle Interface must match when defined by $id, document or reference. The inferred interface based on usage (i.e. we wire a parameter from the parent to the dependency) isn't taken into account for existing installations. TBD if it should be for upgrade/uninstall however.
• The installation's sharing setting must be compatible with the dependency's. The installation may have been created with sharing disabled in which case it must never be reused. Or the dependency's sharing group not matching would also prevent reuse.

Dependencies

• Evaluate a bundle definition against a bundle interface #2626
• Resolve a bundle dependency graph with referenced bundles #2625

ℹ️ Read PEP003 - Advanced Dependencies for context about how dependencies should work, design details, and notes about desired behavior.