ci(build-main): set main NodeJS version to 20 in workflows + set npm …

[mhenkens]

PR Checklist

Please check if your PR fulfills the following requirements:

• The commit message follows our guidelines: https://github.com/NationalBankBelgium/stark/blob/master/CONTRIBUTING.md#-commit-message-guidelines
• Tests for the changes have been added (for bug fixes / features)
• Docs have been added / updated (for bug fixes / features)

PR Type

What kind of change does this PR introduce?

[ ] Bugfix
[ ] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] Build related changes
[X] CI related changes
[ ] Documentation content changes
[ ] Other... Please describe:

What is the current behavior?

GH Workflow is using a deprecated action (upload-artifact@v2) which is deprecated.
More details on: https://github.blog/changelog/2024-04-16-deprecation-notice-v3-of-the-artifact-actions/

The "main" NodeJS version is 18 but we use internally NodeJS 20 to build Stark.

Issue Number: N/A

What is the new behavior?

GH Actions in all workflows are up-to-date.

The main NodeJS version is now 20 and we execute tests on NodeJS 22 also.
Finally, we now depend on the latest [email protected] instead of fixed [email protected].

Does this PR introduce a breaking change?

[ ] Yes
[X] No

Other information

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud