Add mifaser

[vinisalazar]

Description

Adds mifaser for functional annotation of metagenomic reads via EC number assignment (DOI: 10.1093/nar/gkx1209).

Work towards nf-core/funcprofiler#52, nf-core/funcprofiler#58

Notes on container

The bioconda package (mifaser=1.60) and the tool's own container (ghcr.io/vdblab/mifaser:1.64d) have incompatible --databasefolder semantics:

• 1.60 (bioconda/bromberglab): resolves --databasefolder relative to the Python package install directory (os.path.join(pkg_dir, 'database', args.databasefolder)), making it unusable with a user-provided database path unless an absolute path is passed.
• 1.64d (vdblab): resolves the flag as a direct filesystem path, which is the expected behaviour.

This module uses ghcr.io/vdblab/mifaser:1.64d to work around the 1.60 bug. This fails the container_links lint check. A proper fix would require either:

1. A biocontainers-compatible release of mifaser ≥ 1.64, or
2. A patch to the 1.60 bioconda package.

Currently the mifaser code is available on BitBucket: https://bitbucket.org/bromberglab/mifaser/ and version 1.64 is available, but the bioconda recipe points to the PyPI release which is still 1.60

@nickp60 do you think we could set the bioconda recipe to get the tarball from a bitbucket tag endpoint instead? For example, a link from https://bitbucket.org/bromberglab/mifaser/downloads/?tab=tags

[nickp60]

Thanks @vinisalazar! I emailed the authors of Mifaser to ask them to push a new version to pypi. The Bioconda folks want stuff coming direct from Pypi so their recipe updater bots can keep things current.

In the meantime, could you maybe set the command to prepend the database with $PWD in the script section instead so it has an absolute path to work with?

And just FYI their is an official docker container https://hub.docker.com/r/bromberglab/mifaser/tags. I built the ghcr.io/vdblab/mifaser:1.64d container because I needed version tagged versions rather than the "latest" or "dev" tags.