Bump Autodesk.Forge.Core to 4.1.2 (signed release) + add signed-package publish workflow

[MadhukarMoogala]

• Bumps version to 4.1.2 for a signed DLL release (Autodesk code-signing cert via garasign).
• Adds .github/workflows/publish-signed.yml: a workflow_dispatch job that pushes a pre-signed .nupkg (attached as a GitHub Release asset) directly to NuGet.org, without rebuilding. This is needed because garasign requires Autodesk's internal network and cannot run on GitHub-hosted runners.
• Once published to NuGet.org, Autodesk's internal Artifactory (art-bobcat nuget-gallery, a remote cache of nuget.org) will pick up the new signed version automatically on next cache refresh -- no separate Artifactory action needed.

[Copilot]

Pull request overview

Updates the package version for a signed release of Autodesk.Forge.Core and introduces a manual GitHub Actions workflow to publish a pre-signed .nupkg (downloaded from a GitHub Release asset) directly to NuGet.org without rebuilding—supporting signing constraints that can’t run on GitHub-hosted runners.

Changes:

• Bump Autodesk.Forge.Core version from 4.1.1 to 4.1.2.
• Add publish-signed.yml workflow to download a signed .nupkg from a GitHub Release and push it to NuGet.org.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 2 comments.

File	Description
Directory.Build.props	Bumps the package version to 4.1.2 for the signed release.
.github/workflows/publish-signed.yml	Adds a workflow_dispatch pipeline to publish a pre-signed .nupkg from a Release asset to NuGet.org.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[zhuliice]

@MadhukarMoogala thanks for the work! but I don't see .github/workflows/publish-signed.yml gets running, can you check?

[MadhukarMoogala]

Hi @zhuliice

Thanks for reviewing !

that's expected for now. GitHub only allows manually triggering a  workflow_dispatch  workflow once the file exists on  main  (the default branch); it can't be dispatched from a feature branch even if we target this ref. So it won't show up as runnable until this PR merges. Once merged, I'll trigger it against the  v4.1.2-signed  release to actually push the signed package to nuget.org.

happy to do that right after merge for verification.

[zhuliice]

approve, please verify after merge. thanks!