Revert range strategy to "replace"

Per renovatebot/renovate#19800, the "auto" strategy now raises
additional PRs to update dependencies in range. This is either
unsuitable for our use case or bugged, as we have "lockfile update" PRs
(as denoted by a `-lockfile` branch suffix) which are bumping the
in-range version of a package's production dependencies. This means that
e.g. `^2.0.0` gets bumped to `^2.1.0` and so on, and results in a lot of
transitive noise for projects that consume the package.

This _may_ break the previous behaviour of widening peer dependency
ranges, but's a lesser concern now and I'm following up on the Renovate
recommendation for handling this use case.

https://docs.renovatebot.com/release-notes-for-major-versions/#version-35

renovatebot/renovate#20990

default.json

@@ -268,7 +268,7 @@
   "postUpdateOptions": ["yarnDedupeHighest"],
   "prConcurrentLimit": 3,
   "prNotPendingHours": 1,
-  "rangeStrategy": "auto",
+  "rangeStrategy": "replace",
   "schedule": "after 3:00 am and before 6:00 am on Monday and Friday",
   "semanticCommitScope": "",
   "semanticCommitType": "deps",

third-party-major.json

@@ -111,7 +111,7 @@
   "postUpdateOptions": ["yarnDedupeHighest"],
   "prConcurrentLimit": 3,
   "prNotPendingHours": 1,
-  "rangeStrategy": "auto",
+  "rangeStrategy": "replace",
   "schedule": "after 3:00 am and before 6:00 am on Monday and Friday",
   "semanticCommitScope": "",
   "semanticCommitType": "deps"