Loops emailMessageContentRevisionId 409 guard

Trap: updating a Loops campaign email message without persisting emailMessageContentRevisionId looks fine because create returns working IDs immediately, but later edits can fail with 409 Conflict when the revision is stale. Fix: save emailMessageContentRevisionId from campaign creation and send it back as expectedRevisionId on message updates, because Loops uses revision matching for concurrency control.