create bioconda recipe

[GavinHuttley]

base it on the cogent3 one

[khiron]

Can't directly copy the cogent3 recipe as piqtree does not include a source tarball on pypi as cogent3 does.

Cogent3s bioconda recipe uses this.

Working through the bioconda docs to see if I can use a recipe based on the github repo, or link to the build tarballs

[khiron]

The problem appears to be that github release tarballs don't have a SHA256 checksum. I have manually calculated the checksum (shasum -a 256 piqtree-0.4.0.tar.gz) which I'll have to manually redo at every release. Now to see if the PR gets blessed by a bioconda admin - which can take weeks when there is a major update.

I have used the cogent3 fork of bioconda-recipes for now. Happy to work in an iqtree fork of bioconda-recipes if @bqminh forks the repo and grants me permission.

If later when we publish updates to pypi, we also publish the source tarball with SHA256 checksum, then the entire bioconda recipe update process can be automated like the cogent3 one. @rmcar17 would have to bless changes to the publish to pypi workflow to push the source tarball in releases to pypi along with a SHA256 checksum.