chore: bump node from 22 to 24

[soberm]

Description of changes

Bumps Node.js from 22 to 24 across CI workflows, along with all necessary dependency and tooling updates to support the new runtime.

Node.js 24 / npm 11 compatibility:

• Upgrade size-limit and plugins from v8 to v11, removing @size-limit/dual-publish
  • Node 24 ships npm 11, which warns on legacy env configs (version-commit-hooks, version-tag-prefix, etc.) set by Yarn 1.x. The dual-publish package in size-limit v8 treats any stderr output as a fatal error, breaking all test:size tasks. The dual-publish plugin was removed upstream in size-limit v10 since the webpack plugin now handles ESM imports natively.

GitHub Actions Node.js 24 runtime:

Node.js 20 actions are deprecated and will be forced to run on Node.js 24 starting June 2nd, 2026. Updated all actions across 33 workflow files:

Action	Old	New
actions/checkout	v4.0.0 / v4.1.1 / v4.1.3	v6.0.2
actions/cache	v4.2.0	v5.0.3
actions/setup-node	v4.3.0 / v4.4.0	v6.3.0
actions/github-script	v6.4.0 / v7.0.1	v8.0.0
actions/upload-artifact	v4.5.0	v7.0.0
actions/dependency-review-action	v4.7.1	v4.9.0 (still runs on Node 20)

Issue #, if available

N/A

Description of how you validated changes

• CI workflow run on this PR branch
• Verified all old action SHAs are removed from workflow files
• Verified dual-publish is removed from yarn.lock
• No breaking API changes in any of the action upgrades (runtime-only bumps)

Checklist

• PR description included
• yarn test passes
• Unit Tests are changed or added
• Relevant documentation is changed or added (and PR referenced)

Checklist for repo maintainers

• Verify E2E tests for existing workflows are working as expected or add E2E tests for newly added workflows
• New source file paths included in this PR have been added to CODEOWNERS, if appropriate

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

[changeset-bot]

⚠️ No Changeset found

Latest commit: 7c17b06

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR