ci: track Node version with Renovate

[lishaduck]

PR Checklist

• Addresses an existing open issue: fixes #000
• That issue was marked as status: accepting prs
• Steps in CONTRIBUTING.md were taken

Overview

Let Renovate update the versions of Node used in CI, except for the matrix. Which does make me wonder-can we just use a version from package.json?

[changeset-bot]

⚠️ No Changeset found

Latest commit: c0a70a2

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

[netlify]

✅ Deploy Preview for flint-fyi ready!

Name	Link
🔨 Latest commit	c0a70a2
🔍 Latest deploy log	https://app.netlify.com/projects/flint-fyi/deploys/6a83c16f3efa310008078449
😎 Deploy Preview	https://deploy-preview-3200--flint-fyi.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.
🤖 Make changes	Run an agent on this branch

---

To edit notification comments on pull requests, go to your Netlify project configuration.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

[michaelfaith]

why not just use 26, so it just always uses the latest 26? Rather than needing to have renovate update it

[lishaduck]

In general I'd be opposed with the logic that I wouldn't want a Node.js regression to break our builds (as that's been aggravating to me in the past; it can and does happen), but I suppose if the matrix pulls in latest, this doesn't help more 🤔