feat(versioning): same major

[RahulGautamSingh]

Changes

Add a helper function massageVersion which massages single versions to constrains. eg. X.Y.Z as >=X.Y.Z <X+1.0.0

For versioing methods that deal with ranges. The version is massaged to a constraint and then passed to the corresponsing semver-coerced method.

For versioning methods that do not deal with ranges, we directly use the semver coerced methods.

Context

Closes: #27312

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 select one)

I have verified these changes via:

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

[viceice]

shouldn't we name it semver-same-major or semver-coerced-same-major?

Or at least the docs need to clarify that semver-coerced versioning is used under the hood

[secustor]

Nitpick, but not blocking

[HonkingGoose]

The docs are hard to understand.

Please add some examples that explain how it works. Like maybe a diff of "old dependency" vs "proposed Renovate update".

Also focus on the reader, what problem is this feature fixing, how to use/configure it, and how to know if it's working as intended.

[HonkingGoose]

Some style fixes for the current text. I still find this hard to read and understand.