Capability based matching for Adapters #1378
Description
Summary of the new feature / enhancement
AdaptedResource manifests have a hardcoded value for the type name of the adapter, e.g. Microsoft.Adapters/PowerShell. This limits the ability to have different adapters built that may have other benefits that can work with the same adapted resources.
Proposed technical implementation details (optional)
Add a new optional property CompatibleWithAdapter that has the value of an object with typeName and optionally version (which can accept a semver req string). The engine would use this when searching for an adapter. The engine would still apply the "first one wins" rule.
For enterprises, we could add policy for preferred adapters.