Rattler single build, separate suitesparse-devel

[minrk]

Alternative to #98

This is in someways simpler, because it doesn't run separate builds for each library (removes all requirements.build from outputs), it runs a single, unchanged build of all libraries, split into outputs. This adds a suitesparse-devel which has all the cmake/pkgconfig/include files, so most of the library packages are a single file (with symlinks)

But it does require experimental rattler-build features, which means it would likely have to wait for some time. I do think this is the only really feasible way to get separate -devel files, though, so if that's important/desirable, we can hold this until conda-forge tooling is ready for it.

[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 cache is unexpected

For recipe/recipe.yaml:

• ℹ️ It looks like the '???' output doesn't have any tests.

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