GitLab

This change fixes a few places that caused loops of updating sync:
* When sync is applying an update, we now record the network id in a
  map and check before uploading changes from the device.  Previously
  there was only a bit in the metadata store which tracked this, but
  it's not necessarily updated in time.
* When the Network Details page is open and an update is applied, avoid
  re-saving the network from js.
* When applying an update that doesn't include fields that were modified
  by another user, this prevents sync from overwriting the existing
  values (and kicking off another update).  This required adding a new
  option to the proto to leave DNS unspecified.

Bug: 966270
Change-Id: I7a89c0e97b51fbcfd8dea81499fce075a18570eb
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2209892
Commit-Queue: Jon Mann <jonmann@chromium.org>
Reviewed-by: Kyle Horimoto <khorimoto@chromium.org>
Reviewed-by: James Vecore <vecore@google.com>
Reviewed-by: Marc Treib <treib@chromium.org>
Cr-Commit-Position: refs/heads/master@{#772378}