Fix Chromatic action

[tjmw]

What does this change?

I've started seeing errors for the Chromatic action:

error @guardian/braze-components@20.0.0: The engine "node" is incompatible with this module. Expected version "^18.15 || ^20.9". Got "20.8.1"

It seems that the Chromatic action does its own thing with regards to the Node version it uses. The version provided by the setup-node action isn't honoured by Chromatic. Even so, I've moved to using the standard setup-node action and away from the deprecated Guardian setup Node action.

I've slightly loosened the Node version string under engines in package.json, to reflect the version Chromatic seems to be using. This is the real fix to get things working.

Also bump the Chromatic action, which was way behind.

How to test

How can we measure success?

Have we considered potential risks?

Images

Accessibility

• Tested with screen reader
• Navigable with keyboard
• Colour contrast passed
• The change doesn't use only colour to convey meaning

[changeset-bot]

⚠️ No Changeset found

Latest commit: 56afc08

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

[rBangay]

👍