[libarchive] update to 3.8.8

[toge (toge)]

• 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, or no changes were necessary.
• Any fixed CI baseline and CI feature baseline entries are removed from that file, or no entries needed to be changed.
• All patch files in the port are applied and succeed.
• The version database is fixed by rerunning ./vcpkg x-add-version --all and committing the result.
• Exactly one version is added in each modified versions file.

https://github.com/libarchive/libarchive/releases/tag/v3.8.8

[Billy O'Neal (BillyONeal)]

Drafting due to build failures.

GPT-5.5 observes that this update does not build on Windows because libarchive 3.8.8 now references BCryptOpenAlgorithmProvider, BCryptGenRandom, and BCryptCloseAlgorithmProvider from core objects while the vcpkg port still configures -DENABLE_CNG=OFF, so bcrypt.lib is not linked. Local libarchive[core]:x64-windows and the Azure Windows legs fail with unresolved BCrypt* symbols.

[...]

This is introduced by the version update because the PR moves to 3.8.8, whose release notes include “windows: remove support for WinCrypt” and the new core code path now requires CNG linkage on Windows.

Seems like we should force ENABLE_CNG on Windows?