Implement bump mechanism (mostly ported from rye)

[nrbnlulu]

Summary

Implement bump mechanism following major.minor.patch format.
fix #6298

I chose the bump name since version is already used though I would consider removing the current version handler for this

Test Plan

Simple idiomatic tests modifying the test pyprojec and checking the output statically

[nrbnlulu]

windows test is failing though it seems more like a flaky test rather than something related to my changes...

[zanieb]

I'll review this. We'll need to consider what version management interface we want in the long run.

[ThirVondukr]

PEP440 https://peps.python.org/pep-0440/
and commitizen config https://commitizen-tools.github.io/commitizen/commands/bump/#version_scheme
could be good reference points

[zanieb]

I still haven't had time to decide if we want to replace uv version for this.

[nrbnlulu]

Is this PR wanted? should I resolve conflicts?

[n4z4m3]

Is this PR wanted? should I resolve conflicts?

I would find this useful, but I see there has been no action on this for a while. Currently I use bump-my-version to do this, but it would be great to have it built into uv.

[nrbnlulu]

yeah. the maintainers said they want to inspect other project \ alternative interfaces to have better context on this feature.
if someone is interested doing the research it would be cool.

[mthipparthi]

This is great feature and removes the dependency on bump version. This one along with change-log generation makes this tool complete.

[zanieb]

I think about this pretty often, but I'm still not quite sure what to do, e.g., cargo version is not used for this purpose.