Generate plugin schema

[bentsherman]

This PR adds an entrypoint for generating a "plugin index file", which contains a list of plugin definitions (config scopes, functions, etc).

It should be used by the Nextflow Gradle plugin to generate the index file when building/releasing a plugin, and it should be consumed by the plugin registry for use by the language server, registry UI, etc.

[netlify]

✅ Deploy Preview for nextflow-docs-staging canceled.

Name	Link
🔨 Latest commit	dff137f
🔍 Latest deploy log	https://app.netlify.com/projects/nextflow-docs-staging/deploys/68d18c68047355000880c654

[pditommaso]

Does not look to have dependency with the nextflow runtime, does it? could make sense to keep it in its own module or even keep it in the gradle plugin source? it would be preferable to have the gradle plugin to no depend on the main nextflow runtime

[bentsherman]

The PluginIndexWriter does depend pretty heavily on runtime classes, mainly around plugin extensions and config schema. This is why I placed it in a separate configuration, so that the main build doesn't depend on the specific Nextflow version

Long-term, I think we'll want to have a module in Nextflow that defines a versioned "runtime API" that is stable across Nextflow versions. For now I'm just trying to make it work

[bentsherman]

• Add ADR with description of plugin schema (JSON)
• Add unit test

[pditommaso]

Let's use YYYYMMDD as prefix

[pditommaso]

Would not make sense to create a JSON schema for the definition spec? it could be used to have more a "formal" definition and above all to validate it in the upload

[pditommaso]

This is essentially a non-basic type, would not make sense to call it object ?

[bentsherman]

Not sure what you mean by this

[pditommaso]

I mean object instead of children

[bentsherman]

The properties here are based on the domain classes in SchemaNode

[bentsherman]

Okay I have written a JSON schema for plugin "specs"

We need to store this schema somewhere on GitHub so that a plugin spec can refer to it, for example:

{
    "$schema": "https://raw.githubusercontent.com/nextflow-io/nextflow/master/plugin_schema.json",
    "definitions": [
        // ...
    ]
}

We should probably keep it in a separate repo since it is not tied to the Nextflow version. We could extend https://github.com/nextflow-io/schema-spec to include both input/output schemas and plugin schemas