fix: Upgrade dependencies and code to work on new macOS SDK

[queengooborg]

This PR performs a number of updates to make Bambu Studio compile on the latest macOS SDK (14.4 at the time of writing). This fixes #3957.

The particular changes made are the following:

• Bump CGAL to v5.6.1
• Bump Boost to v1.85.0
  • A frozen copy of Boost will no longer need to be maintained!
  • The filesystem/string_file.hpp header was deprecated and had been removed entirely in v1.83.0, so code utilizing it has been replaced
  • Various other methods were deprecated in Boost and have been removed, so they have been replaced according to Boost's suggestions
• wxWidgets:
  • In the wxMediaCtrl2 component, there is an attempt to extend the wxMediaState enum from the original wxMediaCtrl component. The compiler is no longer allowing this, so a new enum is created and used everywhere instead.

Known Issues:

• OCCT
  • OCCT's generated CMake files do not appear to be working, as OpenCASCADEConfig.cmake is requiring files that are not existent. Cause undetermined. Commenting out line 102 (include("${CMAKE_CURRENT_LIST_DIR}/OpenCASCADE${_comp}Targets.cmake")) seems to help.
  • OCCT's header files erroneously import local files using angle bracket syntax rather than quotes (ex. <gp_Lin2d.hxx>, not "gp_Lin2d.hxx"), and the compiler is (now) enforcing this
    • How did this library ever compile, and how have they not fixed this...?
• OpenCV
  • Header files are placed under opencv4/opencv2/*, but we're expecting files to be in opencv2/*. A temporary workaround is manually copying the opencv2 folder and moving it up a folder.
• macOS SDK
  • It appears that a header called WKDownloadDelegate.h, a part of the macOS SDK, requires the macOS target to be at least 11.3. In other words, this means dropping support for 10.15-11.2. It doesn't seem like Bambu Studio is directly using it, but perhaps a dependency is -- this will need to be confirmed.

[MackBambu]

HI,@queengooborg
Thank you for submitting the PR
Has this PR resolved all issues, and is it ready for validation?

[emilazy]

(Uh, very sorry about the notifications spam here, I forgot that GitHub likes to do that whenever you reference an issue in a commit message. Suffice to say that downstream distributors would love to see this brought to completion!)

[queengooborg]

It's alright, those messages don't create emails!

I have mostly stepped away from this PR as my work commitments have taken up the free time I originally had to work on this. It might be best to split this up into smaller chunks and update one or two dependencies per PR. If I remember correctly, this was tricky because newer versions of the libraries wanted C++17.