[Feature] Yarn version should bump all ancestors

Describe the user story

In my project, a package can have a long chain of dependencies which are all the packages in the workspace. If I run yarn version <version> in a package in the chain, it only updates the version of the given package as well as the version in the dependencies field in its direct parents. The version of its parents and ancestors are not bumped.

Take below dependency tree as example:

package A
"version": "1.0.0"

package B
"version": "1.0.0"
"dependencies": {
   "A": "1.0.0"
}

package C
"version": "1.0.0"
"dependencies": {
   "B": "1.0.0"
}

Run yarn version patch in package A. The result will be as below

package A
"version": "1.0.1"

package B
"version": "1.0.0"
"dependencies": {
   "A": "1.0.1"
}

package C
"version": "1.0.0"
"dependencies": {
   "B": "1.0.0"
}

package B and C are not bumped. This result in no available version of package B and C use the version 1.0.1 of package A

Describe the solution you'd like

When bumping a version, all its ancestors should also be bumped. Using the example above, after running yarn version patch in package A. The result should be

package A
"version": "1.0.1"

package  B
"version": "1.0.1"
"dependencies": {
   "A": "1.0.1"
}

package  C
"version": "1.0.1"
"dependencies": {
   "B": "1.0.1"
}

Describe the drawbacks of your solution

Describe alternatives you've considered

Start from the yarn version command and its workspace dependency handling, using the A–B–C dependency tree in the issue as the working example. Trace how direct parents are updated, then identify the logic and tests covering version propagation; done means running the command bumps every workspace ancestor and updates each dependency version consistently.