viz: Remove handles_frame_sink_id_invalidation bit

The handles_frame_sink_id_invalidation bit was introduced because in
the OOP display compositor case, each CompositorFrameSinkSupport handled
its own FrameSinkId invalidation. Now that HostFrameSinkManager has introduced
explicit RegisterFrameSinkId and InvalidFrameSinkId APIs, this bit is no longer
necessary. This CL removes it and updates unit tests accordingly.

Bug: 657959
TBR: [email protected] for content stamp: already reviewed by boliu@ and kenrb@
Cq-Include-Trybots: master.tryserver.chromium.linux:linux_site_isolation
Change-Id: I901614988ada0134cb029a7bbb98f58d94ada337
Reviewed-on: https://chromium-review.googlesource.com/598529
Commit-Queue: Fady Samuel <[email protected]>
Reviewed-by: Sadrul Chowdhury <[email protected]>
Reviewed-by: Bo Liu <[email protected]>
Reviewed-by: Ken Buchanan <[email protected]>
Cr-Commit-Position: refs/heads/master@{#491475}
27 files changed