Migrate recipe to v1 format

[jeongseok-meta]

Summary

• migrate the recipe from the legacy v0 format to the v1 recipe specification
• switch CI generation to rattler-build and bump the build number from 3 to 4
• preserve the source, checksum, cross-compilation patch, dependencies, MAX_JOBS limit, tests, and supported platform matrix

Why

Recipe v1 is valid YAML with a published schema and editor support, has a structure that is easier for automation to update, and avoids recursive rendering. conda-forge supports it through rattler-build, whose Rust implementation also provides faster rendering/builds and clearer payload logs. Both v0 and v1 remain supported; this is a format and build-tool migration with no intended package behavior change.

The conversion makes the v0 semantics explicit: selectors become v1 if/then entries, script_env becomes build.script.env, and the import test becomes a v1 Python test with pip checking left disabled as before. The unsupported v0-only license_family field is omitted while retaining the SPDX license and license file.

On macOS, a freshly extracted native CMake binary can take longer than the five-second scikit-build-core discovery timeout to answer its first capabilities query. Priming CMake once before the build avoids this nondeterministic first-run failure without changing compiler or package behavior. The underlying build-backend limitation is tracked upstream in scikit-build/scikit-build-core#1530.

Validation

• conda-smithy recipe lint passes
• rerendering with conda-smithy 2026.8.9 is idempotent
• render and dependency solve pass for Linux x86_64, Linux aarch64, macOS x86_64, macOS arm64, and Windows x86_64
• a fresh native macOS arm64 Python 3.12 package build and import test pass
• commit subjects and PR title are prefix-free

The local rattler-build run reports existing overdependency warnings for libblas and libcblas. Their host requirements are retained deliberately so this format-only migration does not alter dependency behavior.

This is a draft while the full feedstock CI runs. Please leave it for another maintainer to review before merge.

[conda-forge-admin]

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

I just wanted to let you know that I linted all conda-recipes in your PR (recipe/recipe.yaml) and found it was in an excellent condition.