Rebuild for libboost 1.84

[regro-cf-autotick-bot]

This PR has been triggered in an effort to update boost1840.

Notes and instructions for merging this PR:

1. Please merge the PR only after the tests have passed.
2. Feel free to push to the bot's branch to update this PR if needed.

Please note that if you close this PR we presume that the feedstock has been rebuilt, so if you are going to perform the rebuild yourself don't close this PR until the your rebuild has been merged.

---

If this PR was opened in error or needs to be updated please add the bot-rerun label to this PR. The bot will close this PR and schedule another one. If you do not have permissions to add this label, you can use the phrase @conda-forge-admin, please rerun bot in a PR comment to have the conda-forge-admin add it for you.

_{This PR was created by the regro-cf-autotick-bot. The regro-cf-autotick-bot is a service to automatically track the dependency graph, migrate packages, and propose package version updates for conda-forge. Feel free to drop us a line if there are any issues! This PR was generated by https://github.com/regro/cf-scripts/actions/runs/8596188456, please use this URL for debugging.}

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

[h-vetinari]

So now we come back to #23, because using clang<16 is not compatible with the vs2022 STL anymore, which gets pulled in due to the interaction mentioned here.

[h-vetinari]

@conda-forge-admin, please rerender

[h-vetinari]

So compilation passes now that we're previewing conda-forge/conda-forge-pinning-feedstock#5736 (due to the STL in vs2022 being incompatible with clang<16), however, we're still getting errors in the test suite:

Traceback (most recent call last):
  File "D:\bld\dcgp-python_1712639256632\_test_env\Lib\site-packages\dcgpy\test.py", line 574, in runTest
    pop = algo.evolve(pop)
          ^^^^^^^^^^^^^^^^
TypeError: evolve(): incompatible function arguments. The following argument types are supported:
    1. (self: dcgpy.core.gd4cgp, arg0: pagmo::population) -> pagmo::population

[bluescarni]

So compilation passes now that we're previewing conda-forge/conda-forge-pinning-feedstock#5736 (due to the STL in vs2022 being incompatible with clang<16), however, we're still getting errors in the test suite:

Traceback (most recent call last):
  File "D:\bld\dcgp-python_1712639256632\_test_env\Lib\site-packages\dcgpy\test.py", line 574, in runTest
    pop = algo.evolve(pop)
          ^^^^^^^^^^^^^^^^
TypeError: evolve(): incompatible function arguments. The following argument types are supported:
    1. (self: dcgpy.core.gd4cgp, arg0: pagmo::population) -> pagmo::population

So I think this is due to the fact that pybind11 (used by both dcgp and pygmo to expose C++ classes to Python) forbids convertibility of C++ objects to/from Python across different modules if said modules were not compiled in exactly the same environment, ABI-wise. E.g., see here:

https://github.com/pybind/pybind11/blob/master/include/pybind11/detail/internals.h#L301

In this case, we have an evolve() function in dcgp which takes in input a population object from pygmo. Because dcgp and pygmo were compiled with different compilers/standard libraries, pybind11 is refusing to perform the Python/C++ conversion.

[h-vetinari]

@bluescarni, I'm looking at winding down the boost migration. Is there something we can do to fix the windows failures here (e.g. rebuild everything with a consistent pybind version)?