Update upload-artifact action for the Smoke Test workflow

[RomanNikitenko]

What does this PR do?

At the moment Smoke Test workflow fails for the Che-Code as actions/upload-artifact: v3 was deprecated and it doesn't work starting January 30th, 2025.

So, let's use v4 for the workflow.

What issues does this PR fix?

eclipse-che/che#23325

How to test this PR?

Smoke Test workflow should pass successfully

Does this PR contain changes that override default upstream Code-OSS behavior?

• the PR contains changes in the code folder (you can skip it if your changes are placed in a che extension )
• the corresponding items were added to the CHANGELOG.md file
• rules for automatic git rebase were added to the .rebase folder

[github-actions]

Click here to review and test in web IDE:

[github-actions]

Pull Request images published ✨

Editor: quay.io/che-incubator-pull-requests/che-code:pr-493-amd64
Dev image: quay.io/che-incubator-pull-requests/che-code-dev:pr-493-dev-amd64

[github-actions]

Pull Request images published ✨

Editor: quay.io/che-incubator-pull-requests/che-code:pr-493-amd64
Dev image: quay.io/che-incubator-pull-requests/che-code-dev:pr-493-dev-amd64

[github-actions]

Pull Request images published ✨

Editor: quay.io/che-incubator-pull-requests/che-code:pr-493-amd64
Dev image: quay.io/che-incubator-pull-requests/che-code-dev:pr-493-dev-amd64

[RomanNikitenko]

Smoke Test is still failing because of eclipse-che/che#23328.
Now it's another step - Post Start minikube.
I'm going to fix that problem within a separate PR.

[devspacesbuild]

Build 3.19 :: code_3.x/1546: Console, Changes, Git Data

[devspacesbuild]

Build 3.19 :: sync-to-downstream_3.x/8682: Console, Changes, Git Data

[devspacesbuild]

Build 3.19 :: get-sources-rhpkg-container-build_3.x/8789: Console, Changes, Git Data

[devspacesbuild]

Build 3.19 :: get-sources-rhpkg-container-build_3.x/8789:

code : 3.x :: Failed in 66549520 : code-rhel9-3.19-14
FAILURE: ==> 66549520:DEFAULT:osbs-client.log: <==atomic_reactor.tasks.binary_container_build.BuildProcessError: Build failed (rc=125): Error: creating build container: initializing source docker://registry.redhat.io/ubi9/nodejs-20@sha256:98db77a451a14d6f2fa4f20941ec77952055b784fdab235a4dd382eaf351ce5f: reading manifest sha256:98db77a451a14d6f2fa4f20941ec77952055b784fdab235a4dd382eaf351ce5f in registry.redhat.io/ubi9/nodejs-20: received unexpected HTTP status: 503 Service Unavailableatomic_reactor.tasks.binary_container_build.BuildProcessError: Build failed (rc=125): Error: creating build container: initializing source docker://registry.redhat.io/ubi9@sha256:53d6c19d664f4f418ce5c823d3a33dbb562a2550ea249cf07ef10aa063ace38f: reading manifest sha256:53d6c19d664f4f418ce5c823d3a33dbb562a2550ea249cf07ef10aa063ace38f in registry.redhat.io/ubi9: received unexpected HTTP status: 503 Service Unavailable; copied to quay