`melos version` to support cherry-picks

### Is there an existing feature request for this?

- [X] I have searched the existing issues.

### Command

melos version --fix-changelog

### Description

If having bug fixes or smaller features which are cherry-picked into a separate "release" branch, the changelog is created accordingly. Then the changelog is cherry-picked into the main branch.
Is there some mechanism to avoid having duplicate entries (when doing a further e.g. major release on main) then, or even let melos fix the existing entries by changing the hash of cherry-picked commits?

### Reasoning

Now I have to adapt the changelog manually, to remove duplicate entries / change the hashes.

### Additional context and comments

_No response_

Start with the `melos version --fix-changelog` command and trace how changelog entries and commit hashes are generated. Done means cherry-picked commits do not create duplicate entries and existing entries can use the appropriate cherry-picked hashes when versioning another branch.

Written by the indexing model from the issue text.