feat: Add linting of FASTQ with FQ/LINT

[adamrtalbot]

Checks FASTQ files early in pipeline to catch linting errors.

Simplest possible implementation, which just runs FQ/LINT right now.

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/sarek 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).

[nf-core-bot]

Warning

Newer version of the nf-core template is available.

Your pipeline is using an old version of the nf-core template: 3.0.2.
Please update your pipeline to the latest version.

For more documentation on how to update your pipeline, please see the nf-core documentation and Synchronisation documentation.

[maxulysse]

I'm sure some tests will fails given this new input, but looking nice, thanks for the PR

[maxulysse]

We might want to skip all qc tools in our regular tests, and just do one with all the qc tools.

Stellar work as usual @adamrtalbot

[adamrtalbot]

@maxulysse halp:

ERROR ~ Cannot invoke method split() on null object

[maxulysse]

I'll try to have a look, but I can't promise anything today