Save the rich document (optimistic concurrency)

Saves the doc with the revision the client loaded. A rev mismatch returns 409 with the current server doc so the editor can merge instead of clobbering another writer. Optionally syncs outgoing wiki-link edges in the same save. A tool publishing from an outside source also sends publishedRev, the rev its last publish wrote (easerix#461). If the page has moved past it, people edited it in Notes since, and the save is refused with 409 code edited_since_publish unless force is true. A save that carries publishedRev or force is recorded as a publish (publishedRev/publishedAt on the page). Ordinary saves omit both and are unaffected.

curl -X PUT "https://example.com/v1/pages/497f6eca-6276-4993-bfeb-53cbbbba6f08/doc" \  -H "Content-Type: application/json" \  -d '{    "doc": {},    "rev": 0  }'

{  "rev": 0,  "updated": "2019-08-24T14:15:22Z",  "publishedRev": 0}