ci(dotnet): publish to NuGet with trusted publishing

[ChiragAgg5k]

The .NET SDK template's publish workflow now uses NuGet trusted publishing instead of the NUGET_TOKEN secret, matching appwrite/sdk-for-dotnet#105. Without this, the next generated release would put the expired-key workflow back.

The rendered template is byte-identical to the workflow in that PR. NuGet/login is pinned to v1.2.0 (8d196754), like the other actions in the template.

The NuGet username is read from the NUGET_USER repository variable rather than a secret: it only names the nuget.org account the short-lived key is issued for.

Closes #1975

[hansi-codes]

🟢 Tier S · Ready to merge

No defects found in the incremental change to the NuGet username source.

Updates the generated .NET release workflow to use NuGet trusted publishing instead of the long-lived NUGET_TOKEN secret. The publish job requests OIDC permissions, authenticates through a pinned NuGet/login action using the NUGET_USER repository variable, and pushes packages with the resulting short-lived API key.

Latest changes: The newest commit reads the NuGet username from vars.NUGET_USER instead of secrets.NUGET_USER.

Verdict	New comments	Fixed	Still open
✅ Approved	0	0	0

📂 Walkthrough · 1

File	Change
templates/dotnet/.github/workflows/publish.yml.twig	Adds OIDC permissions and pinned NuGet login, reads the username from a repository variable, and uses the login output for publishing.

---

_{Reviewed the commits since adbc932 · Details · Comment @hansi-codes review to re-run, or mention @hansi-codes with a question.}

[hansi-codes]

🟢 Tier S · Looks good to merge. Summary