[Bug]: API import transactions overrides some fields, not others, hard to make sense

### Verified issue does not already exist?

- [X] I have searched and found no existing issue

### What happened?

when using API to import transactions, if they already exist (**same imported_id**) then an odd behavior happens:

- if the 'updated' transaction has changed amount, it will not take it in account and keep the old one
- if the 'updated' transaction has changed the 'cleared' status, it will use that new status. ommiting the status will force it to True

I do believe it should be the contrary:
- there are good reason to update an amount and it should not be ignored by the import call
- 'Cleared' should not be touched, it's what people use to check operations was reviewed.

selfhosted fresh v23.10.0 servers and client. API version 6.2.1

### What error did you receive?

no error in particular

### Where are you hosting Actual?

Docker

### What browsers are you seeing the problem on?

Chrome, Other

### Operating System

Windows 10