Added rangeStrategy to renovate file

[DineshKumarRA]

User description

Thanks for contributing to Selenium!
A PR well described will help maintainers to quickly review and merge it

Before submitting your PR, please check our contributing guidelines.
Avoid large PRs, help reviewers by making them as simple and short as possible.

Description

Added rangeStrategy to npm and cargo managers as some of the dependencies are not updating package.json or cargo.toml but only the lockfile is getting updated for the dependency upgrade. Adding rangeStrategy should fix this based on renovate documentation - https://docs.renovatebot.com/configuration-options/#rangestrategy

Motivation and Context

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)

Checklist

• I have read the contributing document.
• My change requires a change to the documentation.
• I have updated the documentation accordingly.
• I have added tests to cover my changes.
• All new and existing tests passed.

---

PR Type

Bug fix, Configuration changes

---

Description

• Added rangeStrategy to npm manager for dependency updates.

• Added rangeStrategy to cargo manager for dependency updates.

• Ensures package.json and cargo.toml are updated alongside lockfiles.

• Aligns with Renovate's documentation for consistent dependency management.

---

Changes walkthrough 📝

	Relevant files
Configuration changes	renovate.json Update Renovate configuration for npm and cargo managers  renovate.json Added rangeStrategy: bump to npm manager configuration. Added rangeStrategy: bump to cargo manager configuration. Ensures proper updates to dependency files and lockfiles. +2/-0

---

💡 PR-Agent usage: Comment /help "your question" on any pull request to receive relevant information

[qodo-merge-pro]

PR Reviewer Guide 🔍

Here are some key observations to aid the review process:

⏱️ Estimated effort to review: 1 🔵⚪⚪⚪⚪

🧪 No relevant tests

🔒 No security concerns identified

⚡ No major issues detected

[qodo-merge-pro]

PR Code Suggestions ✨

Explore these optional code suggestions:

Category	Suggestion	Score
General	Using a more conservative range strategy for dependency updates can prevent unexpected breaking changes Consider using 'update-lockfile' or 'pin' instead of 'bump' as the range strategy for npm dependencies to ensure more predictable and stable dependency updates. renovate.json [41-44] "matchManagers": [ "npm" ], -"rangeStrategy": "bump", +"rangeStrategy": "update-lockfile", "commitMessagePrefix": "[js]", "labels": [ "dependencies", "c-nodejs" ] Apply this suggestion Suggestion importance[1-10]: 7 Why: Using 'update-lockfile' strategy is a more conservative approach that can help prevent unexpected breaking changes in npm dependencies while maintaining better version control through lockfiles.	7
	Using an adaptive range strategy allows for more intelligent dependency updates based on package characteristics For Rust/Cargo dependencies, consider using 'auto' instead of 'bump' strategy to let Renovate determine the best update approach based on the dependency type. renovate.json [72-75] "matchManagers": [ "cargo" ], -"rangeStrategy": "bump", +"rangeStrategy": "auto", "commitMessagePrefix": "[rust]", "labels": [ "dependencies", "c-rust" ] Apply this suggestion Suggestion importance[1-10]: 6 Why: The 'auto' strategy for Cargo dependencies is a smart default that can adapt to different package types, though the improvement over 'bump' is moderate as both strategies are valid approaches.	6

[DineshKumarRA]

This should fix the issues with PR like #15001, #15006 where the lockfile is updated but package.json or cargo.toml not updated as ^ means minimum dependency version is met. @diemol @VietND96