window-service: make sure LocalSurfaceId is correctly set

There are two changes here:
. If WindowTree::SetBounds() is called with the same bounds, the LocalSurfaceId
  changes, the LocalSurfaceId needs to be passed down to the embedded client.
  Otherwise the ids aren't in sync.
. When the FrameSinkId is allocated, clients may need to update the
  LocalSurfaceId and tell the server.

These surfaced after the recent removal of EMBED_OWNER. EMBED_OWNER hids these
issues, to a degree.

BUG=none
TEST=covered by test

Change-Id: I5d4d059174b8d5f6d9e3dff056adc15c16438ac4
Reviewed-on: https://chromium-review.googlesource.com/c/1274588
Reviewed-by: Fady Samuel <fsamuel@chromium.org>
Commit-Queue: Scott Violet <sky@chromium.org>
Cr-Commit-Position: refs/heads/master@{#598555}
5 files changed