Modules as plugins

[Julusian]

Follow up items to #3062

Blocking for 4.0:

• Reimplement a 'legacyIds' flow to allow for sensible (but maybe not perfect) upgrading of modules when they are renamed
• Verify that every module that was in 3.5 is available on the store

Optional:

• one click update to latest for an individual module
• allow module version selection during page import?

[krocheck]

@Julusian the store is checking just releases not tags, correct? If so, can we report out modules without a release and/or modules that have at least 1 tag for a version that's newer then the latest release?

[Julusian]

I don't follow what you mean.

The store is telling companion about any modules which have had at least one build successfully published through the developer portal