Audit the version update behavior across ecosystems

[jonjanego]

There are a variety of issues that have been raised indicating inconsistencies with the version update behavior. For example, this issue for pip, which has triggered a potential fix, but it's unclear if this is the right way to handle this, given the long precedent of existing behavior that users rely on.

Instead of making a one-off fix for pip that may result in even more inconsistencies, we instead should undertake an audit of the version update behavior across ecosystems. This will give us a better view into how these options are working across the board, before deciding what (if any) changes we should make to the existing behavior.

Some recent pertinent issues, feel free to link more:

• Enable the widen strategy for Python #6630
• The increase strategy should move ranges forward, not widen them #6631
• Python versioning-strategy of increase does not raise lower version in range #6519
• Changing the lower bound on a requirement without being asked to do so is rude #10130

• https://github.com/github/dependabot-updates/issues/6446
• https://github.com/github/dependabot-updates/issues/6424
• https://github.com/github/dependabot-updates/issues/6558
• https://github.com/github/dependabot-updates/issues/5957
• Document how the Python version is determined and more #10291