Update the forecasted transaction with the specified ID using JSON Patch operations, given that the provided ETag matches. Some fields can only be updated if the forecasted transaction was manually created by a user (origin type USER). For example, if the forecasted transaction was automatically generated from accounting data, the counterpartyId cannot be changed.