dev/release: deploy to NuGet via trusted publishing

### What feature or improvement would you like to see?

> API keys are strongly discouraged for automated publishing and should be replaced with [Trusted Publishing](https://aka.ms/nuget/trusted-publishing), which is currently supported for GitHub Actions, with broader CI/CD support coming soon. We strongly recommend updating now to Trusted Publishing to ensure a seamless transition. For publishing from command line or unsupported CI/CD workflows, [API keys](https://www.nuget.org/account/apikeys?forceApiKeys=true) continue to work.

The issue does not name a file or test; start by locating the GitHub Actions release workflow and its current NuGet publishing configuration. Confirm which automated publishing path uses API keys, then verify that the release completes through NuGet Trusted Publishing without them.

Written by the indexing model from the issue text.