In commits of local branch a push does not refresh the color of the commit

### Describe the bug
In the `Local Branches - Remotes - Tag` window if you are in the local branches and double click to get to its commits, you have an unpushed commit color X, you push it , the color does not change though the commit was pushed. You can esc out to branches and come back in to commits and the color is refreshed to indicate it is no longer local

### To Reproduce
Steps to reproduce the behavior:Provided in description.
### Expected behavior
A color change to reflect a successful commit push

### Version info:

* commit=, build date=, build source=Homebrew, version=0.64.0, os=darwin, arch=arm64, git version=2.55.0

### Terminal info:
What terminal are you using, and which version? For some types of bugs this information can be relevant.

### Additional context
Add any other context about the problem here.

> [!NOTE]
> Please try updating to the latest version or [manually building](https://github.com/jesseduffield/lazygit/#manual) the latest `master` to see if the issue still occurs.

Reproduce the issue in the Local Branches - Remotes - Tag window by opening a local branch's commits, then pushing an unpushed commit. Start with `lazygit --debug` and `lazygit --logs` while tracing the commit view refresh; done means the commit color changes immediately after a successful push without leaving and reopening the view.

Written by the indexing model from the issue text.