Switch to rattler-build

[rgommers]

Checklist

• Used a personal fork of the feedstock to propose changes
• Bumped the build number (if the version is unchanged)
• Reset the build number to 0 (if the version changed)
• Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
• Ensured the license file is being packaged.

Converted automatically with:

conda-recipe-manager convert ./recipe/meta.yaml > ./recipe/recipe.yaml

and then bumped the build number and switched to rattler-build in conda-forge.yml manually.

Reduces build time from 4m 43s in the previous PR to 2m 47s in this PR.

Not yet working locally (pytest tests script doesn't find test files), hence the DEBUG commit and Draft status.

[conda-forge-admin]

Hi! This is the friendly automated conda-forge-linting service.

I wanted to let you know that I linted all conda-recipes in your PR (recipe/recipe.yaml) and found some lint.

Here's what I've got...

For recipe/recipe.yaml:

• ❌ The top level meta key schema_version is unexpected
• ❌ There are 1 too many lines. There should be one empty line at the end of the file.

For recipe/recipe.yaml:

• ℹ️ No valid build backend found for Python recipe for package meson-python using pip. Python recipes using pip need to explicitly specify a build backend in the host section. If your recipe has built with only pip in the host section in the past, you likely should add setuptools to the host section of your recipe.
• ℹ️ noarch: python recipes should usually follow the syntax in our documentation for specifying the Python version.
  • For the host section of the recipe, you should usually use python ${{ python_min }} for the python entry.
  • For the run section of the recipe, you should usually use python >=${{ python_min }} for the python entry.
  • For the test.requires section of the recipe, you should usually use python ${{ python_min }} for the python entry.
  • If the package requires a newer Python version than the currently supported minimum version on conda-forge, you can override the python_min variable by adding a Jinja2 set statement at the top of your recipe (or using an equivalent context variable for v1 recipes).

_{This message was generated by GitHub Actions workflow run https://github.com/conda-forge/conda-forge-webservices/actions/runs/12413397136. Examine the logs at this URL for more detail.}

[rgommers]

Ran into both a rattler-build and a conda-smithy bug here. Plus another invalid linter complaint about a missing build backend that I didn't bother to look at yet (meson-python has an in-tree build backend specified by backend-path in pyproject.toml, so there should not be an external one specified). Let's wait for new rattler-build and conda-smithy releases first.

[rgommers]

@conda-forge-admin, please rerender

[rgommers]

Changing to python_min runs into prefix-dev/rattler-build#1174, so still blocked it looks like.