fix: rerender using new-conda-smithy

[nichmor]

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.

[conda-forge-webservices]

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.

I do have some suggestions for making it better though...

For recipe/recipe.yaml:

This is a rattler-build recipe and not yet lintable. We are working on it!

[baszalmstra]

@conda-forge-admin, please rerender

[github-actions]

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 keys are in an unexpected order. Expecting ['context', 'package', 'source', 'build', 'requirements', 'about', 'extra'].
• The recipe must have some tests.

[github-actions]

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.

[wolfv]

@conda-forge-admin, please rerender

One more time pls!

[wolfv]

@baszalmstra should .dll files go into bin/ or lib/? This package currently installs both dll and lib into lib/.

[wolfv]

This should be iiiit