Renovate config for ni org updates should change package files

[rajsite]

🧹 Tech Debt

The current renovate configuration for NI dependencies (i.e. @ni/fast-* but potentially also eslint config, etc) does a lockfile only change instead of bumping the version in package.json, see:

nimble/.github/renovate.json

Lines 63 to 77 in 2706d74

	"groupName": "npm NI dependencies update to latest",
	"matchManagers": [
	"npm"
	],
	"rangeStrategy": "update-lockfile",
	"matchDepTypes": [
	"dependencies",
	"devDependencies",
	"peerDependencies"
	],
	"matchPackageNames": "@ni/**",
	"schedule": [
	"at any time"
	]
	},

We should instead configure it to bump the package.json versions so that a release of nimble will cause adopters to pick-up the latest version (instead right now it's a transitive dependency that may not need to be picked up).

This will require running npm run change to create change files for the PRs instead of lock file only changes that were previously merged directly.

[jattasNI]

@m-akinc it doesn't look like #2663 worked. We're now getting two PRs when FAST updates:
#2681
#2682

One is for devDependencies and one is for dependencies. Looking closer, it looks like the FAST packages are listed as dependencies, devDependencies, and peerDependencies, depending on which Nimble package depends on them.

I think we need a different strategy in the Renovate config to differentiate these. Maybe calling them out by package name instead of dependency type.