chore(deps): update actions/setup-node action to v4.0.3

[renovate]

This PR contains the following updates:

Package	Type	Update	Change
actions/setup-node	action	patch	v4.0.2 -> v4.0.3

---

Release Notes

actions/setup-node (actions/setup-node)

v4.0.3

Compare Source

---

Configuration

📅 Schedule: Branch creation - "* 0-4 * * 3" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[github-actions]

[puLL-Merge] - actions/setup-node@v4.0.2..v4.0.3

Description

This PR updates several dependencies and makes changes to enhance compatibility with newer Node.js versions. It modifies the CI workflows to use more recent Node.js versions (18, 20, 22) instead of older ones (12, 14, 16). The changes also include updates to various internal libraries and improvements in error handling and HTTP request processing.

Changes

Changes

1. .github/workflows/e2e-cache.yml and .github/workflows/versions.yml:

   • Updated Node.js versions in test matrices from 12, 14, 16 to 18, 20, 22.
   • Updated some test cases to use newer Node.js versions and nightly builds.

2. README.md:

   • Updated examples to use Node.js 20 instead of 16.

3. __tests__/data/:

   • Updated various test files to use Node.js 20 instead of 14.

4. dist/cache-save/index.js and dist/setup/index.js:

   • Various updates to internal libraries, including improvements in HTTP client behavior, header handling, and error processing.

5. package.json:

   • Updated several dependencies to newer versions, including @actions/cache, @actions/http-client, semver, and various dev dependencies.

Possible Issues

1. The changes to Node.js versions in CI workflows might potentially break tests or reveal incompatibilities with older Node.js versions that were previously supported.

2. Updates to internal libraries and dependencies could introduce subtle changes in behavior that might affect the action's performance or compatibility in certain edge cases.

Security Hotspots

No significant security issues are apparent in this change. The updates to dependencies and internal libraries generally improve security by incorporating the latest fixes and improvements.