[Bug]: Rules changing payee don't reflect on both account when creating transactions with API

### Verified issue does not already exist?

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

### What happened?

I created a rule that changes payee to another account. Let's assume there's a rule that matches records from account A, then change the payee to account B.

When I added a transaction that matches that rule via API, specifically using [actual-http-api](https://github.com/jhonderson/actual-http-api), there's only one record in account A. Example of transaction request:
```json
{
"transaction": {
"account": "899a617a-049b-4309-b66f-62b4921220bb",
"amount": -12300,
"date": "2026-01-21",
"category": "e2132cd4-ad33-4449-a562-4dcf361ee8df",
"cleared": true,
"notes": "Some notes"
}
}
```

In the UI it still shows payee pointing to account B. Navigating to account B there's no new record related to the rule, the balance is unchanged.

Expectation: There are 2 records shown both in account A and B, balance of both being updated correctly.

### How can we reproduce the issue?

Create a rule that changes payee to account B when account is account A. Create a transaction via API with the above example request. Observe that only account A has a new record.

### Where are you hosting Actual?

Docker

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

Chrome

### Operating System

Mac OSX