fix: fix dll_name for Authenticode signing in publish workflow

[kinyoklion]

Summary

The sign-dlls step in publish.yml was referencing LaunchDarkly.EventSource.Microsoft.dll, but the assembly is named LaunchDarkly.EventSource (per the csproj AssemblyName), producing LaunchDarkly.EventSource.dll. The signing action was looking for the wrong DLL, so Authenticode signing was not applied.

- dll_name: LaunchDarkly.EventSource.Microsoft.dll
+ dll_name: LaunchDarkly.EventSource.dll

Link to Devin session: https://app.devin.ai/sessions/226ed88b8e8a4434920f2d7e3a49ee61
Requested by: @kinyoklion

---

Note

Low Risk
Single workflow input correction with no runtime or application logic changes.

Overview
The publish workflow’s Sign DLLs step now passes LaunchDarkly.EventSource.dll to sign-dlls instead of LaunchDarkly.EventSource.Microsoft.dll, matching the AssemblyName in the EventSource csproj.

That mismatch meant the signing action never found the built assembly, so Authenticode signing was skipped on release builds.

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

[devin-ai-integration]

🤖 Devin AI Engineer

I'll be helping with this pull request! Here's what you should know:

✅ I will automatically:

• Address comments on this PR. Add '(aside)' to your comment to have me ignore it.
• Look at CI failures and help fix them

Note: I can only respond to comments from users who have write access to this repository.

⚙️ Control Options:

• Disable automatic comment, CI, and merge conflict monitoring