fix: replacement for pep440 versioning

[t-kulmburg]

As requested I am splitting my replacement pr #17476.
This pr makes sure the correct replacementName and replacementVersion are used, as some dependencies didn't get replacements.
It also fixes a problem I encountered with pep440, where now the rangeStrategy handling is skipped when the update is a replacement (used to throw an exception and therefore didn't replace the value).

[JamieMagee]

Can you add any new tests?

[t-kulmburg]

Any updates here? @JamieMagee

[viceice]

This should prbably also be split into 2 PR's:

1. feat: support replacement for pep440
2. fix: use correct values for replacements

[JamieMagee]

If you hit this issue with pep440 versioning, do you think might need this for other versioning schemes that support replacement range strategies?

[JamieMagee]

Needs deconflicting, and potentially a follow-up issue for other versioning schemes, but otherwise looks good to go!

[t-kulmburg]

I did not encounter any problems like this with the other managers/datasources I tested, they are listed here in my README. For the pep440 datasource however there is an Error in versioning/pep440/handleReplaceStrategy, which is fixed/avoided by this PR.
Of course I cannot guarantee that no other problems could pop up, as I only tested one replacement per Manager.

[renovate-release]

🎉 This PR is included in version 34.24.1 🎉

The release is available on:

• GitHub release
• 34.24.1

Your semantic-release bot 📦🚀