Update customers (v4)

Save a member's edits to one customer as its next version; expectedVersion is the version you read (STALE_WRITE if it moved). Fields use the customer model's keys, as business_customers_get_v4's editable fields: a category takes an option id from there or null (else INVALID_INPUT); an open category (occupation, audience, channel, market, buyer role, job, trigger type) may be words in newValues (that option, else a new one for the profile). Age, household income and company size take { value, band }; a changed value sets its band unless the edit does. A changed business employer clears company size and annual revenue unless set. The audience after the edit decides the buyer type: a value it lacks (a consumer's company size, an organization buyer's household) is INVALID_INPUT (CUSTOMER_VERSION_ATTRIBUTE_NOT_APPLICABLE, naming field and buyerType), and a buyer-type change clears such values. A place is geocoded with Mapbox (kept as written if not found). A CRM-connected customer's edited fields are pinned against CRM updates. The customer reruns once on the new version in each live campaign, at once or, while a conversation of theirs runs there, once the campaign can take it (an edit before then joins it, rerun.joinedRequestIds; one after reruns again), as the campaign's run for its current period: its scheduled run, not yet admitted, waits and does not run again; work admitted earlier keeps its version. Paused or held campaigns, one-time studies, Bursts, Pulse, Point11's own campaigns and products Billing would not rerun are skipped (rerun.skipped, Billing's sentence in message); the edit saves regardless.