Test to see if mamba changes impact a known good build

[jim22k]

Checklist

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

NOTE: this is a test PR to verify that the mamba changes in the CI are not causing the broken builds in 6.1.1. Once the PR passes, it should be closed without merging as the build is fully redundant.

[conda-forge-linter]

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) and found it was in an excellent condition.