[DO NOT MERGE] Test new Windows tests against boost 1.82

[traversaro]

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.

[traversaro]

@conda-forge-admin, please rerender

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

[traversaro]

@conda-forge-admin, please rerender

[github-actions[bot]]

Hi! This is the friendly automated conda-forge-webservice.

I tried to rerender for you, but it looks like there was nothing to do.

This message was generated by GitHub actions workflow run https://github.com/conda-forge/gazebo-feedstock/actions/runs/8597561300.

[traversaro]

@conda-forge-admin, please rerender

[traversaro]

@conda-forge-admin, please rerender

[traversaro]

I tested this locally, and it has the exact same problem of boost 1.84 builds, even if we are using boost 1.82 . On the other hand, I built locally gazebo-classic against 1.84, and it is working fine. At this point, I suspect that the difference between working and not working builds is the visual studio version, that got updated at some point between 1.82 and 1.84 builds.

[traversaro]

@conda-forge-admin, please rerender

[traversaro]

Indeed, setting the stdlib version manually to 2019 is working!

[traversaro]

We found the problem, see https://github.com/gazebosim/gazebo-classic/issues/3379 for the whole story.