Fix v1.4-andium MinGW build and v1.4.4 LTS deploy race (#60)

* Pin vcpkg commit for v1.4-andium MinGW build

PR #50 pinned vcpkg to 84bab45 (OpenSSL 3.6.0) for the v1.4.4 LTS job to
fix its Windows MinGW build, but left the sibling v1.4-andium job on the
default vcpkg (OpenSSL 3.5.0), whose make install step is incompatible
with the windows-2025 MSYS2/MinGW toolchain. Apply the same pin so
v1.4-andium builds OpenSSL 3.6.0 too. The Linux side is already covered
by the perl-core build prerequisite added in #50.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>

* Fix v1.4.4 LTS deploy depending on the wrong build job

duckdb-lts-deploy deploys the v1.4.4 artifacts but declared
`needs: duckdb-stable-build` (the v1.5.3 build) instead of
`needs: duckdb-lts-build`. It therefore started as soon as the stable
build finished and raced the LTS build's artifact upload: on runs where
the LTS build finished later, the deploy failed with "Artifact not found
for name: ui-v1.4.4-extension-osx_amd64". Point it at duckdb-lts-build so
it waits for the build that produces the artifacts it deploys.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>

---------

Co-authored-by: Claude Opus 4.8 <noreply@anthropic.com>