add module bbmap/clumpify

[erkutilaslan]

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/seqinspector branch on the nf-core/test-datasets repository.
• [ ] Make sure your code lints (nf-core lint).
• [ ] Ensure the test suite passes (nf-test test main.nf.test -profile test,docker).
• [ ] 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).

[erkutilaslan]

this commit is without nf-tests I will do another pull request after running nf-tests

[MatthiasZepper]

For the future: You could have left the PR open or converted it back into a draft PR. By pushing more commits to the respective branch, you can also modify it after opening.

I would also recommend creating a new feature branch for every new feature that you are developing, so instead of committing and pushing your changes to the dev branch of your fork, to create a separate branch with git checkout -b "name_of_your_branch"

You can also edit the base and reference branches, so reopen this PR instead of a new one. As you like.