Submitting `biaplotter` to conda-forge

[bruno-pannunzio]

Hi biaplotter team,

I maintain napari-phasors, a napari plugin that depends on biaplotter. I'm packaging napari-phasors for conda-forge so it can be bundled into a standalone installer, and biaplotter isn't on conda-forge yet — so I've submitted a recipe for it alongside my own package in the same staged-recipes PR (conda-forge requires interdependent recipes to be submitted together).

A few things:

• The recipe is auto-generated from PyPI metadata via grayskull and only packages the existing release as-is — no code changes.
• conda-forge's process lists me as the initial feedstock maintainer, since I'm the one submitting it. I'd be happy to hand over or share maintainership with you/the BiAPoL team if you'd like to be listed too. Just let me know and I'll add you to extra: recipe-maintainers before merge, or you can request access on the feedstock afterward.
• Maintenance is low-effort: conda-forge's autotick bot opens an automatic version-bump PR whenever you publish a new release to PyPI; someone just needs to merge it.

Let me know if you have any concerns about this, or if you'd rather maintain the feedstock yourselves going forward. Thanks for the great package!