fix: use >| instead of >

[znorgaard]

See issue for details. tldr > > redirect pattern can count as a clobber in some environments / with certain versions of bash. Using >| > temporarily ignores the clobber check.

I also needed to fix the rseqc env files to get linting to pass, conda-forge::r-base>=3.5 -> conda-forge::r-base=3.5

PR checklist

Closes #8455

• This comment contains a description of changes (with reason).
• If you've fixed a bug or added code that should be tested, add tests!
• 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

[znorgaard]

[In progress]

Modules failing testing due to nextflow-io/nextflow#5456

• angsd/contamination docker test: reproduced locally. It's specifically the stub test that fails. conda env with nextflow=24.10.2 nf-test=0.9.2 causes failure. Using latest of both the test passes. nf-test test --profile "docker" --verbose modules/nf-core/angsd/contamination/tests