New module: regtools junction extract

[abartlett004]

PR checklist

New module for regtools junction extract

Closes #7032

• [X] This comment contains a description of changes (with reason).
• [X] If you've fixed a bug or added code that should be tested, add tests!
• [X] If you've added a new tool - have you followed the module conventions in the contribution docs
• [X] If necessary, include test data in your PR.
• [X] Remove all TODO statements.
• [X] Emit the versions.yml file.
• [X] Follow the naming conventions.
• [X] Follow the parameters requirements.
• [X] Follow the input/output options guidelines.
• [X] Add a resource label
• [X] 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:
  • [X] 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

[lpantano]

@mashehu, can you take a quick look in case we are missing something? thanks!

[SPPearce]

Linting fails: nf-core modules lint regtools/junctionsextract

And it didn't run at all?

[SPPearce]

@edmundmiller, while you are here can you check why nf-core modules lint didn't notice the lack of versions (or wasn't ran at all)?

[edmundmiller]

Just started looking into this because it should've triggered the wave CI, but it didn't 🙃

Ah, it's coming from a fork, and that's why.

[lpantano]

@SPPearce, do you have any other comment?

[edmundmiller]

Updated the regex and tested the versions.

Gonna skip the CI on this one, should be fixed in #7043

[SPPearce]

@SPPearce, do you have any other comment?

No, happy now (although as Edmund had approved that was sufficient)