Add support for upcoming Boost 1.87.0 (Boost.Asio removals)

[cho-m]

Advance notice that Monero does not compile with upcoming Boost 1.87.0 (based on beta1) as Boost.Asio has removed the deprecated io_service boostorg/asio@ec0908c

This causes errors like:

contrib/epee/include/net/net_utils_base.h:33:10: fatal error: 'boost/asio/io_service.hpp' file not found
   33 | #include <boost/asio/io_service.hpp>
      |          ^~~~~~~~~~~~~~~~~~~~~~~~~~~

And impacts all usage of boost::asio::io_service (along with various other removed functions/methods)

io_service was deprecated in favor of io_context back in 1.66.0 (boostorg/asio@b60e92b). Easiest approach is to require a minimum of Boost 1.66.0 and use newer APIs. Otherwise, would need to create many #if BOOST_VERSION ... conditions for compatibility.

Related: https://www.boost.org/doc/libs/1_86_0/doc/html/boost_asio/net_ts.html

[tobtoht]

Boost 1.87.0 was released a few days ago, so this will start breaking development builds and CI soon.

I'm not very familiar with this part of the codebase. @vtnerd maybe?

[0xFFFC0000]

that io_service to io_context for boost is going to be a huge PR. We are using io_service in 381 different place, and as asio dev are saying the change is not backward compatible. boostorg/asio#110

[vtnerd]

There's more than just the io_service removal in this version of boost, so it's going to be rough change. As someone mentioned, we should probably bump the minmum boost version, some of the changes are going to be a tough to workaround otherwise.

[tobtoht]

We can bump the minimum to 1.66.0 per #9446 and a PR to bump boost in release builds from 1.64.0 to 1.84.0 is ready.

[vtnerd]

I'm working on a patch using Boost 1.66-1.87 as the target. Lots of changes being made, so it may take a while to test them.

[vtnerd]

See #9628