Add 19.41 support

[isuruf]

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 code>@<space/conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
• [ ] Ensured the license file is being packaged.

[conda-forge-webservices[bot]]

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/meta.yaml) and found some lint.

Here's what I've got...

For recipe/meta.yaml:

• Package version is missing.

[conda-forge-webservices[bot]]

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

[github-actions[bot]]

Hi! This is the friendly conda-forge automerge bot!

I considered the following status checks when analyzing this PR:

• linter: passed
• azure: passed

Thus the PR was passing and merged! Have a great day!

[jdblischak]

They briefly updated it ... and reverted it

@isuruf it looks like they've updated the image again. This morning my build was failing because it installed vs2022_win-64 19.41 in image version 20240811.1.0 (Visual Studio 17.10). Now that vs2022_win-64 19.41 has been marked as broken (https://github.com/conda-forge/admin-requests/pull/1056), I restarted the job, and it failed because it installed vs2022_win-64 19.40 in image version 20240825.1.0 (Visual Studio 17.11).

I always find these image updates hard to pinpoint since the actual update on Azure is unrelated to when the docs PR is merged (https://github.com/actions/runner-images/pull/10490 is still open).

xref: failing Azure build with changing image versions, https://github.com/TileDB-Inc/conda-forge-nightly-controller/issues/133#issuecomment-2313257891

[isuruf]

Mind sending a PR to mark them unbroken?

[jdblischak]

Sure. I'll do that now

[jdblischak]

This is chaos. Azure keeps switching the image version. Last night at 9:30 pm ET it was using 20240825.1.0 (Visual Studio 17.11), but then exactly 12 hours later this morning at 9:30 am ET, it reverting to using image version 20240811.1.0 (Visual Studio 17.10).

My questions are:

• Should we report this upstream? It's hard to imagine that only conda-forge jobs are being disrupted by the random switching between Visual Studio 17.10 and 17.11. I couldn't find any open Issue. The closest thing I could find was this Issue requesting Visual Studio 17.11 https://github.com/actions/runner-images/issues/10448

• Is there any way to make this recipe (or conda itself) aware of the version(s) of Visual Studio available on the machine? These errors happen every time Azure updates the version of Visual Studio in its image. Having to exactly align our vc-feedstock release with their image update is difficult, to say the least. I assume it won't be possible, but I wanted to at least raise the idea

xref: https://github.com/TileDB-Inc/conda-forge-nightly-controller/issues/133#issuecomment-2315592291

[jdblischak]

Unfortunately it looks like we can't pin the exact image version for the Azure build, so that isn't an option as a short-term workaround https://github.com/actions/runner-images/discussions/3464