Update boost to 1.83.0

[Kudo]

Summary:

Since folly is updated from 17154a6, it is good to bump boost too.

After updating boost, we can remove the Xcode 15 _LIBCPP_ENABLE_CXX17_REMOVED_UNARY_BINARY_FUNCTION workaround which originally to fix Xcode 15 for boost.

Changelog:

[GENERAL][CHANGED] - Update boost to 1.83.0

Test Plan:

• CI passed
• Build and launch RNTester on Android and iOS

[cipolleschi]

Thanks @Kudo for taking care of this! 🙌

[cipolleschi]

This PR is based on #39552. Not sure how Meta internally deal with stacked PRs. This PR just adds a new commit based on #39552 anyway.

I think that this PR contains all the changes that are in #39552, so we can land this one only. Could you double-check that as well?

[facebook-github-bot]

@cipolleschi has imported this pull request. If you are a Meta employee, you can view this diff on Phabricator.

[Kudo]

I think that this PR contains all the changes that are in #39552, so we can land this one only. Could you double-check that as well?

that's correct! good to know we can just land this one. let me update this pr's description/changelog and close #39552.

[analysis-bot]

Platform	Engine	Arch	Size (bytes)	Diff
android	hermes	arm64-v8a	8,333,695	-210
android	hermes	armeabi-v7a	n/a	--
android	hermes	x86	n/a	--
android	hermes	x86_64	n/a	--
android	jsc	arm64-v8a	9,573,167	-174
android	jsc	armeabi-v7a	n/a	--
android	jsc	x86	n/a	--
android	jsc	x86_64	n/a	--

Base commit: 7888338
Branch: main

[facebook-github-bot]

@cipolleschi merged this pull request in b9f0bdd.

[liamjones]

Something I've just noticed in relation to this PR when upgrading from 0.72.x to 0.73.x - if the _LIBCPP_ENABLE_CXX17_REMOVED_UNARY_BINARY_FUNCTION directive had been added to a project previously, it doesn't get removed again here.

Is that an issue or not? I noticed it's a CXX17 directive and 0.73 moves to c++20 so maybe it isn't obeyed anyway?

[cipolleschi]

@liamjones it should not be an issue. The directive is needed to backport the name of an API that has changed. I don't think that it's an issue if we keep it. Unless you are seeing some specific errors: if that's the case, could you share them?

[liamjones]

@cipolleschi Nope, not seeing any errors. I just noticed it wasn't being removed when I did the RN upgrade and wanted to check if it was deliberate. Thanks for confirming it was! 😄