Move `conda-recipe/recipe.yaml` to main repo

[Czaki]

Currently, each time we update pyproject.toml, there is a need to make a PR here. May we move conda-recipe/recipe.yaml to live in a main repo and implement a a pre-commit hook or CI check (using a Python script) to enforce consistency between pyproject.toml and recipe.yaml?

We may even trigger a build from the main repo if dependecies changed.

https://github.com/napari/packaging/blob/main/conda-recipe/recipe.yaml

cc @jaimergp ?

[jaimergp]

I don't personally mind. It would just complicate iteration when we want to iterate on installer contents (e.g. the move to pyside6 now).

So if you want to have the recipe over there, we may also merge packaging with napari so all the infra is in the same place. We split them at the beginning so we could decouple responsibilities between teams, but there's no explicit bundle working group anymore, so there's no need either.

[Czaki]

I don't personally mind. It would just complicate iteration when we want to iterate on installer contents (e.g. the move to pyside6 now).

In such a case, we could just copy the file again to the repository in PR?

[jni]

My preference would be to make the pyproject.toml workflow more clever. Basically, whatever you implement to make a pre-commit hook, which needs to be pretty involved (check whether it's a dependency that's changed or something irrelevant to this repo, map pypi to conda-forge names), you can use to check whether you need to make an issue, and maybe even to auto-open the PR.