update snakemake-wrapper-utils to 0.5.2

[dlaehnemann]

Mainly, this is an update to snakemake-wrapper-utils version 0.5.2. But poetry changed the file naming of the sdist files (.tar.gz) in its build command, and that is what is uploaded to pypi for snakemake-wrapper-utils. The long story is in one of the commit messages, that I reproduce here for better findability and cross-references on GitHub:

Make package name in sdist .tar.gz filename conform to specs (using underscores)

The official specs for sdist file names require that the package name is in snake case, see these places:

• https://peps.python.org/pep-0625/#specification
• https://packaging.python.org/en/latest/specifications/binary-distribution-format/#escaping-and-unicode
• https://peps.python.org/pep-0491/#escaping-and-unicode

poetry switched to conforming to these specs with version 1.2.2, see:

• poetry-core pull request with the actual code changes: Normalize sdist filenames python-poetry/poetry-core#484
• poetry pull request pulling them in: normalized sdist names python-poetry/poetry#6621

Thus, all (bio-)conda recipes whose sources are built with poetry and uploaded to pypi are likely to face the same issue.

As snakemake-wrapper-utils only contains hyphens (-) as non-word characters, the suggested replace("-","_") should be safe and enough.

But a thorough solution should be implemented in grayskull (that does conda recipe templating for pypi packages), and in the tooling of conda-forge and bioconda. One solution to make such recipes more future-proof would be to make tooling respect the official guidance to query the pypi JSON API to get download urls. Examples of how to do this are here:

• stackoverflow answer with example code of querying the pypi JSON API for a download URL
• link to the pypi code for generating the currently used standardized redirect links at pypi.io, that also uses the JSON API

---

Please read the guidelines for Bioconda recipes before opening a pull request (PR).

• If this PR adds or updates a recipe, use "Add" or "Update" appropriately as the first word in its title.
• New recipes not directly relevant to the biological sciences need to be submitted to the conda-forge channel instead of Bioconda.
• PRs require reviews prior to being merged. Once your PR is passing tests and ready to be merged, please issue the @BiocondaBot please add label command.
• Please post questions on Gitter or ping @bioconda/core in a comment.

Please use the following BiocondaBot commands:

Everyone has access to the following BiocondaBot commands, which can be given in a comment:

@BiocondaBot please update	Merge the master branch into a PR.
@BiocondaBot please add label	Add the please review & merge label.
@BiocondaBot please fetch artifacts	Post links to CI-built packages/containers. You can use this to test packages locally.

For members of the Bioconda project, the following command is also available:

@BiocondaBot please merge

Upload built packages/containers and merge a PR. Someone must approve a PR first! This reduces CI build time by reusing built artifacts.

Also, the bot watches for comments from non-members that include @bioconda/<team> and will automatically re-post them to notify the addressed <team>.