Create or run companies transactions bulk approve

Success envelope. data is the bulk summary (requested, processed, skipped, failed, results with one item per distinct id) plus stripeRevenueStillHeld (#3039): the ids of Stripe counterparty-history suggestions that this request approved, or found already categorized on their suggested account, and whose Stripe revenue entry still has no account to post to after the request tried to write their merchant rule (the write failed, or the merchant or account cannot carry a rule). Those rows read categorized while their revenue stays held; send the same request again (a signed-in accountant's request writes the missing rule of an already categorized suggestion and reports the row as skipped), or use the single approve route. Empty when there is none. An already categorized suggestion whose revenue account resolves is left alone and its existing rule is not changed. Split rows are approved status-only, get no rule and are never listed here. Bulk-approve never changes an existing merchant rule (decided before any row is written): a suggestion still in review whose Stripe revenue account already resolves is approved with no rule write when that account is the suggested one, and comes back as a failed result, untouched, with reason This Stripe revenue row's customer already has a rule or revenue account that differs from the suggested one; review it individually when it is another account. The same failed result is returned, on the in-review path and on the already-categorized retry path, when the customer's exact merchant rule already exists and names another account of any type (for example an expense account, which gives no revenue authority); when that rule names the suggested account, no rule is written. A rule is never moved to another account by this route: it is created, or rewritten with the account it already names. A row whose account, merchant rule or revenue authority cannot be read is likewise not approved: failed, reason "This Stripe revenue row's merchant rule could not be checked; it was not approved. Try again". Selected suggestions that would write the same merchant rule with different suggested accounts all come back failed, untouched, with reason Selected Stripe revenue rows from the same customer suggest different accounts; approve them individually; with the same account they are approved and share one rule.