Fix KmerFinder DB and relative paths resolution issues

[Daniel-VM]

trafficstars

PR checklist

• [X] 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/bacass branch on the nf-core/test-datasets repository.
• [X] Make sure your code lints (nf-core pipelines lint).
• [X] 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.
• [x] CHANGELOG.md is updated.
• [ ] README.md is updated (including new tool citations and authors/contributors).

PR Description

This PR addresses path-related issues when processing the input samplesheet:

• Fixed incorrect KmerFinder database paths
• Resolved errors with symbolic links and local paths

Close #215