Json schema improvements

[andreirie]

PR checklist

• This comment contains a description of changes (with reason).
• If you've fixed a bug or added code that should be tested, add tests!
• If you've added a new tool - have you followed the pipeline conventions in the contribution docs
• If necessary, also make a PR on the nf-core/funcscan branch on the nf-core/test-datasets repository.
• Make sure your code lints (nf-core pipelines lint).
• Ensure the test suite passes (nextflow run . -profile test,docker --outdir <OUTDIR>).
• Check for unexpected warnings in debug mode (nextflow run . -profile debug,test,docker --outdir <OUTDIR>).
• Usage Documentation in docs/usage.md is updated.
• Output Documentation in docs/output.md is updated.
• CHANGELOG.md is updated.
• README.md is updated (including new tool citations and authors/contributors).

[github-actions]

This PR is against the master branch ❌

• Do not close this PR
• Click Edit and change the base to dev
• This CI test will remain failed until you push a new commit

---

Hi @andreirie,

It looks like this pull-request is has been made against the andreirie/funcscan master branch.
The master branch on nf-core repositories should always contain code from the latest release.
Because of this, PRs to master are only allowed if they come from the andreirie/funcscan dev branch.

You do not need to close this PR, you can change the target branch to dev by clicking the "Edit" button at the top of this page.
Note that even after this, the test will continue to show as failing until you push a new commit.

Thanks again for your contribution!

[jen-reeve]

Since you aren't releasing a new version, just adding to whatever the next release is, you don't need to set up a new dev tag. Just leave #v2.2.0dev and include your changes there. Typically, a new release will include more than just some tidying up. See the recent Sarek JSON improvement PR for an example.

[andreirie]

Thanks for the advice.

[nvnieuwk]

Suggested change

	## v2.1.1 - Brazilian André - [date]
	## v2.2.0dev - [date]

[nvnieuwk]

One comment, please ping me on Slack if you have fixed it

[nvnieuwk]

LGTM!