Use v1 schema

[bollwyvl]

Comment:

The v1 format (using rattler-build) would give us some nice maintainer features (faster, better YAML). Currently blocked by:

• v1 recipe and channel_sources and priority conda-smithy#2226

  • needed for prereleases e.g. notebook-feedstock

• Ignores channel_sources rattler-build-conda-compat#67
• support menuinst icons
  • landed in rattler-build 0.37.0

Some of the developer benefit (build speed) could be traded in for other benefits:

• zstd_compression_level

  • setting to 22 takes an extra ~20s, but cuts the final .conda package size in half

[bollwyvl]

Of note, uploading a package with an icon presently broken, even with conda-build:

• conda-forge package uploads failing when icon is present due to missing pillow anaconda-client-feedstock#57
• jupyterlab 4.4.0b1 #467
• https://dev.azure.com/conda-forge/feedstock-builds/_build/results?buildId=1197972&view=logs&j=7b6f2c87-f3a7-5133-8d84-7c03a75d9dfc&t=9eb77fd2-8ddd-5444-8fc0-71cb28dcb736&l=2446

[bollwyvl]

Removing icon on #468

[bollwyvl]

Restored app (whoops) on #469. Turns out there is a slightly better way with https://conda-forge.org/docs/maintainer/conda_forge_yml/#remote-ci-setup that would work with re-rerender, but hopefully this all blows over after a few more PRs...