🔧 Repository: Renovate Node Version Updates

### 📜 Description

Renovate currently will try and create a PR to update Node types and the engines to the latest node version. This isn't ideal as we want to support a range and also give Plugin Owners the ability to handle this change.

The down side to just closing the PR is that now the types may not get the updates they need.

Example PR: https://github.com/backstage/community-plugins/pull/7812

### 👍 Expected behavior

Renovate will generate PRs for just the Node type packages and not change the engines property in the package.json file

### 👎 Current Behavior

Renovate generates a PR that updates both the types and the engines property in the package.json file

### 👟 Reproduction steps

N/A

### 📃 Provide the context for the Bug.

This isn't ideal as we want to support a range and also give Plugin Owners the ability to handle this change.

### 👀 Have you spent some time to check if this bug has been raised before?

- [x] I checked and didn't find similar issue

### 🏢 Have you read the Code of Conduct?

- [x] I have read the [Code of Conduct](https://github.com/backstage/community-plugins/blob/main/CODE_OF_CONDUCT.md)

### Are you willing to submit PR?

No, but I'm happy to collaborate on a PR with someone else

Start by reviewing the repository's Renovate configuration and example PR #7812, then inspect the affected package.json files. Done means Renovate updates the Node type packages while leaving each package's engines property unchanged.

Written by the indexing model from the issue text.