ci: bump OpenSSL Chocolatey pin to 4.0.3

[kinyoklion]

Summary

Fixes the Windows CI jobs by moving the OpenSSL Chocolatey pin to a version whose installer can still be downloaded.

• Since 2026-09-30, every Windows job on main (server-sdk, server-sdk-curl, redis, dynamodb, otel) fails in install-openssl.
• choco install openssl --version 4.0.2 downloads https://slproweb.com/download/Win64OpenSSL-4_0_2.exe, and that URL now returns 404.
• The pin moves from 4.0.2 to 4.0.3, the current Chocolatey latest. Its installer URL returns 200.

Implementation details

This is the same failure as #601. slproweb only hosts the installer for the current release, so any old Chocolatey pin breaks once a newer OpenSSL ships. Failing log from the nightly libs/server-sdk run: https://github.com/launchdarkly/cpp-sdks/actions/runs/36836152742

• Checked today: the Win64OpenSSL-4_0_3.exe URL returns 200, and the 4_0_2, 3_6_0 and 3_5_4 URLs return 404.
• The only change is in .github/actions/install-openssl/action.yml.
• A follow-up could stop the pin going stale again: for example, drop --version or use a source that keeps older installers.

Link to Devin session: https://app.devin.ai/sessions/ee398be9fea84ae6a72d896ad30d8cc8
Open in Devin Desktop: https://app.devin.ai/desktop/session/ee398be9fea84ae6a72d896ad30d8cc8?variant=devin

SDK-3263

---

Note

Overview
Windows CI was failing in the install-openssl composite action because Chocolatey’s pinned OpenSSL 4.0.2 installer URL on slproweb now returns 404 (same pattern as prior pin rot).

The only code change updates .github/actions/install-openssl/action.yml from choco install openssl --version 4.0.2 to 4.0.3, so Windows runners can download a current installer again and set OPENSSL_ROOT_DIR as before.

^{Reviewed by Cursor Bugbot for commit 8af034d. Bugbot is set up for automated code reviews on this repo. Configure here.}

[devin-ai-integration]

I'll fix CI failures and address comments from users with write access. I'll skip comments containing "(aside)".

• Disable automatic comment, CI, and merge conflict monitoring

[cursor]

Cursor Bugbot has reviewed your changes using default effort and found 1 potential issue.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, have a team admin enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit 8af034d. Configure here.}