I want Plugin URIs to be clearly defined, not arbitrarily

[dOrgJelli]

Motivation

Currently, plugin URIs are defined in a arbitrary way, which can easily break composability as the Polywrap development ecosystem grows and decentralizes. We should have tailored developer experience that ensure plugin URIs are not arbitrary, and are defined in clearly understandable ways.

Sub-Stories & Sub-Tasks

• [ ] As a plugin developer, I want to implement an interface (new or existing)
  • [ ] Link plugin projects to an external interface
  • [ ] Link plugin projects to a local interface
• [ ] As an app developer, I should not be responsible for defining the URI a plugin implements
  • [ ] Plugins should (optionally) have a self-assigned URI, which points to the interface they implement
  • [ ] Client plugin registration should not require a URI, if the plugin self-assigns it
• [ ] As a wrapper developer, I want to depend on plugins in a transparent way
  • [ ] Wrapper developers are able to import & invoke plugins given their interface's URI
  • [ ] Wrapper developers are able to import & invoke plugins given their pre-bundled wrap.info

[dOrgJelli]

@polywrap/dev feedback requested

[nerfZael]

LGTM