vcpkg port checklist for v0.8.2

[mario4tier]

The vcpkg talib port needs a real update at 0.8.2, not just a version and SHA512 bump: #423 makes the build install a CMake package config, which changes what the port must do and lets its hand-written wrapper go away.

• Update the vcpkg port for 0.8.2, in one PR: bump the version and SHA512, ship upstream's CMake config instead of the port's own wrapper, drop the Windows static rename, and settle MinGW support. The details, and what was measured, are in the comment below.

It cannot be done before 0.8.2 is published: the port builds the released ta-lib-<ver>-src.tar.gz, and the CMake config only exists from 0.8.2 onward.

[mario4tier]

Probed the whole 0.8.2 shape against dev 9af18dd31 (run 35116765234, throwaway branch, now deleted): port = dev source + vcpkg_cmake_config_fixup(PACKAGE_NAME ta-lib CONFIG_PATH lib/cmake/ta-lib), no hand-written wrapper, consumer on find_package(ta-lib) + ta-lib::ta-lib with both include spellings, Debug and Release.

• All 11 curated triplets (x86/x64/arm64 Windows, release-only, static, static-md, arm64-osx and -dynamic, x64-linux and -dynamic): install clean under --enforce-port-checks, and the consumer builds and runs. No post-build warnings, and the config lands in share/ta-lib.
• The Windows static rename is what breaks: keeping it, x64-windows-static and -static-md install fine and then the consumer dies at configure, because ta-lib-config.cmake points at debug/lib/ta-lib-static.lib, which the rename removed.
• x64-mingw-static installs clean. x64-mingw-dynamic fails only the obsolete-CRT check. The MinGW consumer result in that run is not evidence: the harness compiled it with the host gcc rather than the cross toolchain.

[mario4tier]

Details for the port update, with what each item rests on. Probed against dev 9af18dd31 (runs 35114473041 and 35116765234, throwaway branches, now deleted).

• vcpkg_cmake_config_fixup(), plus the vcpkg-cmake-config host dependency. cmake: install a package config so find_package(ta-lib) works #423 makes the build install lib/cmake/ta-lib/ta-lib-config*.cmake, and vcpkg fails the port for it: "installs CMake files in places CMake files are not expected" and "creates lib/cmake ... use vcpkg_cmake_config_fixup()". This hits every triplet, not just the ones below.
• Delete vcpkg-cmake-wrapper.cmake once the real config is fixed up, and decide what happens to the current entry points: the port exports find_package(talib) with talib::talib, while upstream exports find_package(ta-lib) with ta-lib::ta-lib. Either keep a thin compatibility wrapper for one release or state the break in the PR.
• Drop the Windows static rename entirely. Measured: with the exported config, ta-lib::ta-lib records the installed file name, so renaming ta-lib-static.lib to ta-lib.lib leaves the target pointing at a file that no longer exists and every Windows static consumer fails at configure. Without the rename, x64-windows-static and -static-md install and consume cleanly. (It also removes the MinGW file RENAME failed problem, so no MinGW guard is needed.)
• Decide supports for MinGW. Measured with the fixup in place: x64-mingw-static installs cleanly, and x64-mingw-dynamic fails only on vcpkg's obsolete-CRT check, since MinGW DLLs link msvcrt.dll; that needs VCPKG_POLICY_ALLOW_OBSOLETE_MSVCRT in the portfile or the triplet. Either leave supports as it is (static works, dynamic is a community triplet vcpkg CI never builds), or add the policy line, or exclude MinGW. Earlier context: MinGW now gets past configure, since cmake: install a package config so find_package(ta-lib) works #423's release removes the vcvarsall Platform requirement, so the old reason to exclude it is gone. x64-mingw-static then failed only on the CMake-files checks above. x64-mingw-dynamic additionally trips "DLLs that link with obsolete CRT" (MinGW links msvcrt.dll), which needs VCPKG_POLICY_ALLOW_OBSOLETE_MSVCRT in the triplet or the portfile; community triplets are not built by vcpkg CI either way.
• Re-run the local triplet matrix before submitting, as for 0.8.1: x-test-features on the CI triplets plus a consumer built through the installed CMake config, both include spellings.

scripts/post-release-vcpkg.py prepare still handles the version and SHA512; everything above is hand work on top of it.