Define API how a plugin indicates its capabilities to the dashboard

There are a number of places in the dashboard UI where the status and capabilities of a plugin are expressed. For example, a plugin may have the capability of installing a feature into the Hippo project, it may provide a UI to configure a certain aspect of the Hippo project, and/or it may require a rebuild of the project or dashboard before the plugin UI can be rendered or used.

We need to define how the plugin communicates these capabilities to the dashboard. Which aspects need to be communicated? At what stage of the plugin installation process? Consider plugin-descriptor-bloat vs. maintenance of a separate, runtime API.