fix: rangeStrategy=replace with lockedVersion

[rarkins]

Changes:

Fixes an edge case where:

• rangeStrategy=replace
• A range is in use
• A lock file is in use
• The locked version is not the highest version matching the range, or the same version as the range

In such scenarios the incorrect result was a PR which essentially "bumped" the range to start with the current locked version.

Context:

Closes #9627

Documentation (please check one with an [x])

• I have updated the documentation, or
• No documentation update is required

How I've tested my work (please tick one)

I have verified these changes via:

• Code inspection only, or
• Newly added unit tests, or
• No new tests but ran on a real repository, or
• Both unit tests + ran on a real repository

[rarkins]

Confirmed that the new test failed against master without this fix. Also confirm against a fork of JustinBeckwith/linkinator

[rarkins]

Example:

• range is ^1.0.0
• locked version is 1.1.0
• 1.2.0 is also available

The result would be that the range is bumped to ^1.1.0

[renovate-release]

🎉 This PR is included in version 24.119.3 🎉

The release is available on:

• GitHub release
• 24.119.3

Your semantic-release bot 📦🚀