Update bcftools

[saramonzon]

PR checklist

Related to nf-core/viralrecon#466

• 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 module conventions in the contribution docs
• If necessary, include test data in your PR.
• Remove all TODO statements.
• Emit the versions.yml file.
• Follow the naming conventions.
• Follow the parameters requirements.
• Follow the input/output options guidelines.
• Add a resource label
• Use BioConda and BioContainers if possible to fulfil software requirements.
• Ensure that the test works with either Docker / Singularity. Conda CI tests can be quite flaky:
  • For modules:
    • nf-core modules test <MODULE> --profile docker
    • nf-core modules test <MODULE> --profile singularity
    • nf-core modules test <MODULE> --profile conda
  • For subworkflows:
    • nf-core subworkflows test <SUBWORKFLOW> --profile docker
    • nf-core subworkflows test <SUBWORKFLOW> --profile singularity
    • nf-core subworkflows test <SUBWORKFLOW> --profile conda

[saramonzon]

@SPPearce thanks for your patience and PR reviews xD

one question, linting tests are not passing for bam_ngscheckmate subworkflow

│ Subworkflow name  │ File path                                      │ Test message                                    │
│╶──────────────────┼────────────────────────────────────────────────┼────────────────────────────────────────────────╴│
│ bam_ngscheckmate  │ subworkflows/nf-core/bam_ngscheckmate/tests/m… │ md5sum for empty file found:                    │
│                   │                                                │ d41d8cd98f00b204e9800998ecf8427e       

these empty md5sum are already present in the repo, how did you manage to pass the linting check? I saw it was you who migrate this subworkflow to nf-test. Should I try to fix this? I added the tags the linting aseked for but i don't know if i should change all this md5sum checks to just the filename. There are 9 of them, this is an example:

 "0": [
                    [
                        {
                            "id": "test_bed"
                        },
                        "test_bed_output_corr_matrix.txt:md5,d41d8cd98f00b204e9800998ecf8427e"
                    ]
                ],
                "1": [
                    [
                        {
                            "id": "test_bed"
                        },
                        "test_bed_matched.txt:md5,d41d8cd98f00b204e9800998ecf8427e"
                    ]
                ],
                "2": [
                    [
                        {
                            "id": "test_bed"
                        },
                        "test_bed_all.txt:md5,d41d8cd98f00b204e9800998ecf8427e"
                    ]
                ],

[SPPearce]

Hmm, let me take a look at bam_ngscheckmate. They shouldn't be empty there.

[saramonzon]

I've tried to fix it in the last commit. I don't know why the vcf can't be collected, it's also empty now and fails to collect.
Take a look, and tell me if you'd fix it any different.
thanks!

[SPPearce]

I have a vague memory that the subworkflow linting wasn't working properly at some point.