[folly] Delete FindLibUnwind.cmake

[jimwang118]

Fixes #36971

Delete FindLibUnwind.cmake and do not search for the LibUnwind library.

• Changes comply with the maintainer guide.
• SHA512s are updated for each updated download.
• The "supports" clause reflects platforms that may be fixed by this new version.
• Any fixed CI baseline entries are removed from that file.
• Any patches that are no longer applied are deleted from the port's directory.
• The version database is fixed by rerunning ./vcpkg x-add-version --all and committing the result.
• Only one version is added to each modified port's versions file.

Usage and feature test pass with following triplets:

x64-linux

[jiayuehua]

should also add patch that delete line 156-161 https://github.com/facebook/folly/blob/7c77eef4df2fd8ff3d37ccf190ad2a6d4b5e7e08/CMake/folly-deps.cmake#L156

[jimwang118]

should also add patch that delete line 156-161 https://github.com/facebook/folly/blob/7c77eef4df2fd8ff3d37ccf190ad2a6d4b5e7e08/CMake/folly-deps.cmake#L156

Is there any problem with deleting FindLibUnwind.cmake files directly?

[jiayuehua]

line156 will use FindLibUnwind.cmake ,the file that deleted.

[jimwang118]

line156 will use FindLibUnwind.cmake ,the file that deleted.

Yes, therefore LIBUNWIND_FOUND=false will be returned, FOLLY_HAVE_LIBUNWIND:ON will not be set, and issue will not occur.
This has the same final result as deleting find_package(libunwind).

[jiayuehua]

I see.

[dg0yt]

The real question whether it wouldn't be enough to CMAKE_DISABLE_FIND_PACKAGE_LibUnwind.
But the new change matches the existing pattern in this port, so leave as is.

[BillyONeal]

Thanks :)