This updates the CI/CD workflow to use the `upload-artifact` v4 and
`download-artifact` v4 GitHub Actions. The currently used `upload-artifact`
and `download-artifact` will no longer work at the end of next month.
The changes are needed since v4 no longer has mutable artifacts, which
was used to collect wheels from different architectures.

Fixes #8588, fixes #8589, fixes #9009, fixes #10189, fixes #10191.

PR #10281.

(cherry picked from commit d54b3e2)

This updates the CI/CD workflow to use the `upload-artifact` v4 and
`download-artifact` v4 GitHub Actions. The currently used `upload-artifact`
and `download-artifact` will no longer work at the end of next month.
The changes are needed since v4 no longer has mutable artifacts, which
was used to collect wheels from different architectures.

Fixes #8588, fixes #8589, fixes #9009, fixes #10189, fixes #10191.

PR #10281.

(cherry picked from commit d54b3e2)

…ifact v4 and download-artifact v4 (#10289)

**This is a backport of PR #10281 as merged into master
(d54b3e2).**

<!-- Thank you for your contribution! -->

## What do these changes do?

This updates the ci/cd workflow to use the upload-artifact v4 and
download-artifact v4 github actions. The currently used upload-artifact
and download-artifact will no longer work at the end of next month.
The changes are needed since v4 no longer has mutable artifacts, which
was used to collect wheels from different architectures.

Fix #8588, Fix #8589, Fix #9009, Fix #10189, Fix #10191 

## Are there changes in behavior for the user?

No, the ci/cd workflow has been tested although without publishing. 

## Related issue number

<!-- Are there any issues opened that will be resolved by merging this
change? -->
<!-- Remember to prefix with 'Fixes' if it should close the issue (e.g.
'Fixes #123'). -->

## Checklist

- [x] I think the code is well written
- [ ] Unit tests for the changes exist
- [ ] Documentation reflects the changes
- [ ] If you provide code modification, please add yourself to
`CONTRIBUTORS.txt`
  * The format is &lt;Name&gt; &lt;Surname&gt;.
  * Please keep alphabetical order, the file is sorted by names.
- [x] Add a new news fragment into the `CHANGES/` folder
  * name it `<issue_or_pr_num>.<type>.rst` (e.g. `588.bugfix.rst`)
  * if you don't have an issue number, change it to the pull request
    number after creating the PR
    * `.bugfix`: A bug fix for something the maintainers deemed an
      improper undesired behavior that got corrected to match
      pre-agreed expectations.
    * `.feature`: A new behavior, public APIs. That sort of stuff.
    * `.deprecation`: A declaration of future API removals and breaking
      changes in behavior.
    * `.breaking`: When something public is removed in a breaking way.
      Could be deprecated in an earlier release.
    * `.doc`: Notable updates to the documentation structure or build
      process.
    * `.packaging`: Notes for downstreams about unobvious side effects
      and tooling. Changes in the test invocation considerations and
      runtime assumptions.
    * `.contrib`: Stuff that affects the contributor experience. e.g.
      Running tests, building the docs, setting up the development
      environment.
    * `.misc`: Changes that are hard to assign to any of the above
      categories.
  * Make sure to use full sentences with correct case and punctuation,
    for example:
    ```rst
    Fixed issue with non-ascii contents in doctest text files
    -- by :user:`contributor-gh-handle`.
    ```

    Use the past tense or the present tense a non-imperative mood,
    referring to what's changed compared to the last released version
    of this project.

Co-authored-by: Simon Lamon <[email protected]>

…ifact v4 and download-artifact v4 (#10288)

**This is a backport of PR #10281 as merged into master
(d54b3e2).**

<!-- Thank you for your contribution! -->

## What do these changes do?

This updates the ci/cd workflow to use the upload-artifact v4 and
download-artifact v4 github actions. The currently used upload-artifact
and download-artifact will no longer work at the end of next month.
The changes are needed since v4 no longer has mutable artifacts, which
was used to collect wheels from different architectures.

Fix #8588, Fix #8589, Fix #9009, Fix #10189, Fix #10191 

## Are there changes in behavior for the user?

No, the ci/cd workflow has been tested although without publishing. 

## Related issue number

<!-- Are there any issues opened that will be resolved by merging this
change? -->
<!-- Remember to prefix with 'Fixes' if it should close the issue (e.g.
'Fixes #123'). -->

## Checklist

- [x] I think the code is well written
- [ ] Unit tests for the changes exist
- [ ] Documentation reflects the changes
- [ ] If you provide code modification, please add yourself to
`CONTRIBUTORS.txt`
  * The format is &lt;Name&gt; &lt;Surname&gt;.
  * Please keep alphabetical order, the file is sorted by names.
- [x] Add a new news fragment into the `CHANGES/` folder
  * name it `<issue_or_pr_num>.<type>.rst` (e.g. `588.bugfix.rst`)
  * if you don't have an issue number, change it to the pull request
    number after creating the PR
    * `.bugfix`: A bug fix for something the maintainers deemed an
      improper undesired behavior that got corrected to match
      pre-agreed expectations.
    * `.feature`: A new behavior, public APIs. That sort of stuff.
    * `.deprecation`: A declaration of future API removals and breaking
      changes in behavior.
    * `.breaking`: When something public is removed in a breaking way.
      Could be deprecated in an earlier release.
    * `.doc`: Notable updates to the documentation structure or build
      process.
    * `.packaging`: Notes for downstreams about unobvious side effects
      and tooling. Changes in the test invocation considerations and
      runtime assumptions.
    * `.contrib`: Stuff that affects the contributor experience. e.g.
      Running tests, building the docs, setting up the development
      environment.
    * `.misc`: Changes that are hard to assign to any of the above
      categories.
  * Make sure to use full sentences with correct case and punctuation,
    for example:
    ```rst
    Fixed issue with non-ascii contents in doctest text files
    -- by :user:`contributor-gh-handle`.
    ```

    Use the past tense or the present tense a non-imperative mood,
    referring to what's changed compared to the last released version
    of this project.

Co-authored-by: Simon Lamon <[email protected]>