fix: Ensure Lighthouse plugin upgrade is done even if site is pinned to earlier major

[Skn0tt]

No description provided.

[netlify]

✅ Deploy Preview for netlify-plugins ready!

Name	Link
🔨 Latest commit	34ceee8
🔍 Latest deploy log	https://app.netlify.com/sites/netlify-plugins/deploys/65b924ac89291b0009ac1d4c
😎 Deploy Preview	https://deploy-preview-1302--netlify-plugins.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

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

[conventional-commit-lint-gcf]

🤖 I detect that the PR title and the commit message differ and there's only one commit. To use the PR title for the commit history, you can use Github's automerge feature with squashing, or use automerge label. Good luck human!

-- conventional-commit-lint bot
https://conventionalcommits.org/

[eduardoboucas]

There's not a lot of context to go by, but I'm assuming you've tested that the upgrade is safe.

[eduardoboucas]

I think the formatting is off here.

[Skn0tt]

There's not a lot of context to go by, but I'm assuming you've tested that the upgrade is safe.

I did! The only change is that we're changing the node engine compatibility from >=14.15 <20 to >= 18.14. And since we're currently doing the upgrade from 18 to 20 for the system version (the version used to run the plugins from plugin.json), both are within the new compatibility.