Switch from push-to-main auto-release to GitHub Releases-triggered publishing

[Copilot]

Publishing was triggered automatically on every merge to main using GitVersion for versioning. The new model gates publishing behind an explicit GitHub Release, using the release tag as the canonical version source for both the NuGet and npm packages.

Changes

.github/workflows/dotnet.yml

• Stripped GitVersion, version-stamping, dotnet pack, and dotnet nuget push steps
• Now purely a CI workflow (build + test) for pushes to main
• Updated action pins: actions/checkout, actions/setup-dotnet → @v4

.github/workflows/release.yml (new)

• Triggers on release: published
• Extracts semver from tag, stripping leading v (e.g. v1.2.3 → 1.2.3)
• Stamps C# project via roryprimrose/set-vs-sdk-project-version@v1
• Stamps npm package via npm version --no-git-tag-version
• Builds and tests both targets in Release configuration
• Uploads .nupkg as a release asset
• Publishes to NuGet.org (NUGET_API_KEY secret) and npmjs.org (NPM_TOKEN secret)

Original prompt

---

This section details on the original issue you should resolve

<issue_title>Change the .github workflow</issue_title>
<issue_description>We want the github workflow to be changed.

We should not create automaticly a release on merge to master, we should use the release page to create one.
If we create one there, we should use the version from the tag, and use it in the c# nuget and npm package to publish the version to the repositorys

Similar like we did in https://github.com/dotnetprojects/Migrator.NET</issue_description>

Comments on the Issue (you are @copilot in this section)

• FixesChange the .github workflow #30

---

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.