ci: Fix artifact handling for GitHub Actions v4 (backport #52)

[mergify]

PR Type

What kind of change does this PR introduce?

• Build or CI related changes

What is the current behavior?

With latest change to update to download-artifact and upload-artifact to v4, only 1 artifact is now downloaded for the publication
Related previous PR: ci: Update download-artifact and upload-artifact to v4 #51

What is the new behavior?

• Updated artifact upload steps to assign unique names (NuGet-Fluent, NuGet-Roboto, NuGet-OpenSans) to address changes introduced in actions/upload-artifact@v4.
• Modified publish job to download artifacts by job-scoped names into separate directories (artifacts/fluent, artifacts/roboto, artifacts/opensans).
• Adjusted signing and pushing steps to ensure consistent handling of artifacts across jobs and publishing.

Note

Related details:

• https://github.blog/changelog/2024-02-13-deprecation-notice-v1-and-v2-of-the-artifact-actions/
• https://github.blog/news-insights/product-news/get-started-with-v4-of-github-actions-artifacts/

PR Checklist

Please check if your PR fulfills the following requirements:

• Tested code with current supported SDKs
• Docs have been added/updated which fit documentation template. (for bug fixes / features)
• Unit Tests and/or UI Tests for the changes have been added (for bug fixes / features) (if applicable)
• Wasm UI Tests are not showing unexpected any differences. Validate PR Screenshots Compare Test Run results.
• Contains NO breaking changes
• Updated the Release Notes
• Associated with an issue (GitHub or internal)

---

This is an automatic backport of pull request #52 done by [Mergify](https://mergify.com).

[mergify]

Cherry-pick of 28b88be has failed:

On branch mergify/bp/release/stable/2.4/pr-52
Your branch is up to date with 'origin/release/stable/2.4'.

You are currently cherry-picking commit 28b88be.
  (fix conflicts and run "git cherry-pick --continue")
  (use "git cherry-pick --skip" to skip this patch)
  (use "git cherry-pick --abort" to cancel the cherry-pick operation)

Unmerged paths:
  (use "git add <file>..." to mark resolution)
	both modified:   .github/workflows/ci.yml

no changes added to commit (use "git add" and/or "git commit -a")

To fix up this pull request, you can check it out locally. See documentation: https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/checking-out-pull-requests-locally

[agneszitte]

@Mergifyio refresh

[mergify]

refresh

✅ Pull request refreshed