The CL:
https://chromium-review.googlesource.com/c/chromium/src/+/1256964

Introduced a change in how browsingData.remove works on desktop.

On desktop platforms, Sync now requires a Google cookie to work.

browsingData.remove is designed to clear data both locally and on the Sync server. In order to be able to clear data on the server, the google account cookie used by Sync will be rebuilt after the cookies are cleared, so that the data (like history) can be deleted on the server.
This is only done if Sync is enabled and working.

This needs to be called out in the documentation, because it may be surprising for a user to clear the cookies through the browsingData.remove API and see that there is still a cookie left after the operation.

Other cookie-clearing APIs are not affected (i.e. browsingData.removeCookies).

Note: Chrome OS was not changed. The cookie rebuild does not happen there.