Improving contributor pixi task UX

[ruben-arts]

As a package contributor I find myself learning a few commands by head. Because of that I have a few proposals to make it easier for new/ocasional contributors to start out with this repo.

Having a non docker build task

I like to use rattler-build directly to make it easier/faster to run changes in the recipe.
What I would need is a task that helps me setup a rattler-build command .e.g:

[tasks.build]
description = "Build v1 recipes into conda packages directly on the host machine"
cmd = ["rattler-build", "build", 
       "--variant-config", ".ci_support/{{ pixi.platform | replace('-', '_') }}.yaml",
       "--output-dir", "build_artifacts",
       "--recipe-dir", "recipes/"]

I need to changes in the repo to make this work:

• Rename the .ci_support/*.ymls to acutally use the platform name e.g. osx-64 instead of osx64
• Move the recipes/example-v1 out of the recipes folder. As rattler-build doesn't support a skip option for that.

Remove the v0 recipe from the main user flow

Since the v1 recipe is the successor of the conda-forge recipes. I think it should be clear to the users.

• Remove the grayskull tasks for v0
• Remove the example form the recipes folder
• Strip out more of the conda-build related tooling.

Keeping a seperate environment for that workflow might make sense to move away from it more slowly.

What do you think? I would be open to do the work involved to make this conda-forge UX better.