Use org NuGet publish secret

[peters]

Summary

• replace the personal-named NuGet.org publish secret with FINTER_NUGET_ORG_API_KEY
• keep the package publish workflow behavior unchanged

Tracking: fintermobilityas/youpark.no#12240

Validation

• git diff --check
• GitHub Actions must pass before merge

Notes

• No package publish workflow was triggered.
• The new org secret is selected to surge and mongomigrations.core only.

[Copilot]

Pull request overview

Updates the NuGet publish step in the CI workflow to use an organization-scoped NuGet.org API key secret (FINTER_NUGET_ORG_API_KEY) instead of the previously personal-named secret, preserving existing publish behavior.

Changes:

• Switched dotnet nuget push to authenticate with ${{ secrets.FINTER_NUGET_ORG_API_KEY }} in the package publish step.

---

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

[peters]

CI is green, but GitHub blocks normal merge by repository policy and auto-merge is disabled for this repository. I am leaving this open rather than using admin bypass.