Modules meta.yml ontology

[mirpedrol]

Follow up from #3028
Split into a different PR to make it easier to review once #3028 is merged
I closed #3028 so this is the only PR to review now

Continuation of #2789

This PR adds an automated way of generating the right format meta.yml for modules.

 input: 
   - - meta: 
           type: map 
           description: | 
             Groovy Map containing sample information 
             e.g. [ id:'test', single_end:false ] 
       - scaffold: 
            type: file 
            description: Fasta file containing scaffold 
            pattern: "*.{fasta,fa}" 
   - - fasta: 
           type: file 
           description: FASTA reference file 
           pattern: "*.{fasta,fa}" 

Note that the structure proposed in nf-core/modules#4983 (comment) is not possible if we want to automate the creation of this file, as comments are ignored when reading a yaml file with Python.

Example of outputs formatting:

output:
  - versions:
    - "versions.yml":
        type: file
        description: File containing software versions
        pattern: "versions.yml"
  - bam:
    - meta:
        type: map
        description: Groovy Map containing sample information
  
    - "*.bam":
        type: file
        description: Sorted BAM/CRAM/SAM file
        pattern: "*.{bam,cram,sam}"

In this PR we also add an option --update-meta-yml --fix to fix existing files automatically.
To be changed to --fix as suggested in #2789 (comment)

Pytests are also missing for this functionality.
A test was added for the command nf-core modules lint --fix. ⚠️ This test will fail until the JSON schema is updated (nf-core/modules#5837)

Together with this PR, there are other actions which must happen at the same time:

• Updating the JSON schema used for lining module and subworkflows meta.yml files update JSON schema for modules meta.yml modules#5837
• Update the documentation
• Add the same changes for subworkflows Add option --fix to update the meta.yml file of subworkflows. #3077
• Add a mention of bio.tools and EDAM ontologies for inputs and outputs Modules meta.yml ontology #3032

This PR also adds a tool identifier to the modules meta.yml. It queries bio.tools to obtain the bio.tools ID.
It adds the edam ontologies for file inputs and outputs to the meta.yml template.

Note that ontologies are not automatised, even though this can sometimes be obtained from bio.tools.
Currently, inputs and outputs are not automatically obtained when first creating the module. We should consider if it is required to automatise this.
One option is to update the ontologies when updating the meta.yml with --update-meta-yml

POC in modules: nf-core/modules#5867

Ontologies can be added manually, and we have linting for them, but we leave implementing the tooling for a later stage: #3027

[maxulysse]

some conflicts 😨

[ewels]

Suggested change

	f"Incorrect inputs specified in module `meta.yml`. Inputs should contain: {correct_inputs}\nRun `nf-core modules lint --fix` to update the `meta.yml` file.",
	f"Module `meta.yml` does not match `main.nf`. Inputs should contain: {correct_inputs}\nRun `nf-core modules lint --fix` to update the `meta.yml` file.",

[ewels]

Suggested change

	f"Incorrect outputs specified in module `meta.yml`. Outputs should contain: {correct_outputs}\nRun `nf-core modules lint --fix` to update the `meta.yml` file.",
	f"Module `meta.yml` does not match `main.nf`. Outputs should contain: {correct_outputs}\nRun `nf-core modules lint --fix` to update the `meta.yml` file.",

[ewels]

Reviewed and tested over zoom, LGTM after final check about schema ✅