Create or run companies transactions approve

#3046: why the category was changed. One line of plain text (trimmed; no control, line-separator or text-direction characters, no HTML markup, and not the text '| Recategorization reason:'). Stored as the reasoning of the decision on the transaction timeline and appended to the replacement journal entry's description as ' | Recategorization reason: <reason>'. Absent leaves the decision as before and removes a reason left on the description by an earlier recategorize; a description that never carried one is unchanged. The reason is not sent to QuickBooks.

#3041: whether this approval writes or repoints the merchant rule for this transaction's merchant. true: a changed category does. Absent: a changed category, including the first category on an uncategorized transaction, applies to this transaction only and the rule is left alone; an approval that leaves the category unchanged writes a rule only when it confirms a Stripe counterparty-history suggestion. false: no rule is written in any case. Stripe revenue transactions (a Stripe charge, invoice or subscription payment, or a Stripe counterparty-history suggestion) are outside this choice: a category change on one always writes its exact company rule, because that rule is what lets the revenue entry post. The bookkeeping engine's feedback run is queued whatever the value; its output is a proposal for review.