Uploadlist 'resets' immediatly after a conflict resolve decision and starts all over again

### ⚠️ Before posting ⚠️

- [X] This is a **bug**, not a question or an enhancement.
- [X] I've [searched for similar issues](https://github.com/nextcloud/android/issues) and didn't find a duplicate.
- [X] I've written a clear and descriptive title for this issue, not just "Bug" or "Crash".
- [X] I agree to follow Nextcloud's [Code of Conduct](https://nextcloud.com/contribute/code-of-conduct/).

### Steps to reproduce

1. Have a lot of uploads with conflicts to resolve in autoupload
2. Resolve one by 'keeping server version'

You´re in this situation when moving from one phone to another with your files and keep the same folders and settings.

### Expected behaviour

After a conflict resolve decision, this one entry for the file is either:
(keep local) added to the upload list and removed from conflict list, immediatly visible
(keep server) do nothing [download file? *unclear] and remove from conflict list
This without reseting the rest of the actual upload and conflict list. And not to start all over again hopefully with one file less.

### Actual behaviour

After a conflict resolve decision, a few seconds later. The whole upload list restarts and the whole conflict list is reset (to 0) and has to recreate/is recreating the left conflicts. (By the way this produces far to much traffic and workload, unnecessarily.)
Also, if I can do the resolve of another file, bevor it resets, and do it in the wrong moment it is completely ignored. (Counted the numbers, sometimes it worked)

Additionally, as long as the top of the conflict list is constant it doesn't restart. Why does it matter at all?
Most of the time it is continuously showing different files while the number of conflicts goes up.

### Android version

12

### Device brand and model

Motorola Edge 30 Neo

### Stock or custom OS?

Stock

### Nextcloud android app version

3.22.3

### Nextcloud server version

I´m not the admin, probably 20 at that time.

### Using a reverse proxy?

No

### Android logs

_No response_

### Server error logs

_No response_

### Additional information

I made screen recordings, but they are not eligible to be uploaded here.
#255 hash compare could already cover up the situation, but does not change the bad behaviour of unnecessarily reseting the lists (to early).