Create branch with no nextflow-schema.json for training purposes

[kenibrewer]

Hi @adamrtalbot ,

As part of our progressive approach to training, I thought it might be good to create a separate protected branch, no-nextflow-schema or something similar, that is missing the nextflow-schema.json.

This would serve two functions:

1. During the hello-nfcore training module, we can have folks fork this repo (and checkout the branch). After they learn how to build the nextflow_schema.json they can push it to their fork. CC @vdauwera on this idea
2. During the hello-seqera training module, we can have folks first add this repo to the launchpad and see the default interface. After they switch the branch to the nextflow-schema branch (or add their fork) they would see the rendered interface.

Alternatively, we could have the missing nextflow-schema.json on the main branch.

[adamrtalbot]

Easy enough to implement! We can also name it something weird on main then use the custom schema path on the platform to correct it.

[adamrtalbot]

Done here: https://github.com/seqeralabs/nf-hello-gatk/tree/no-nextflow-schema