Fix bakta: amrfinder database issue

[jasmezz]

This fixes a crash of bakta when using the automatically downloaded database with bakta (reported here).
It does not seem to be a conda-only issue. I could reproduce it with singularity as well, that's why I execute the amrfinder_update line regard of the profile.

(The memory requirement in the config file was decreased only because GHA complained.)

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 module conventions in the contribution docs
• If necessary, include test data in your PR.
• Remove all TODO statements.
• Emit the versions.yml file.
• Follow the naming conventions.
• Follow the parameters requirements.
• Follow the input/output options guidelines.
• Add a resource label
• 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:
    • 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

[christopher-mohr]

LGTM!

[jasmezz]

Thanks for checking, @christopher-mohr! 🚀