ci: Use 'replace' rangeStrategy to prevent unintended dependency pinning

The previous 'pin' rangeStrategy caused several issues:
* It unexpectedly pinned exact versions of dependencies in the distributed `package.json` files.
* It also automatically updated the Node.js version and engine ranges to their latest versions, which was not the desired behavior for our CI/CD pipeline.

Switching to the 'replace' strategy resolves these problems, ensuring more predictable and stable dependency management within our CI setup.

See: angular#31062

Author: alan-agius4

renovate.json

@@ -5,7 +5,7 @@
   "stopUpdatingLabel": "action: merge",
   "labels": ["action: review"],
   "dependencyDashboard": true,
-  "rangeStrategy": "pin",
+  "rangeStrategy": "replace",
   "prHourlyLimit": 3,
   "commitBody": "See associated pull request for more information.",
   "timezone": "America/Tijuana",