windows: updates kApplyNativeOcclusionToCompositor

It turns out evicting the current frame and/or hiding the Compositor
without doing anything extra results in preventing some resources
from being released/freed. In order to enable freeing of the resources
a minimal compositor frame needs to be submitted.

This patch removes the existing three variations and adds two
new ones:
release: this removes the root cc::Layer and adds a solid color layer,
         waits for the frame to be generated, adds back the real root
         layer, and hides the compositor.
throttle: when the window is occluded the frame rate is throttled.
          This variation won't release resources, but it should
          limit the amount of work done in occluded windows.

BUG=1248235
TEST=covered by tests

Change-Id: Ic94314af7b85d3a0797ee9ebc6ccbdedd1df66e4
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3273706
Reviewed-by: David Bienvenu <davidbienvenu@chromium.org>
Reviewed-by: John Abd-El-Malek <jam@chromium.org>
Commit-Queue: Scott Violet <sky@chromium.org>
Cr-Commit-Position: refs/heads/main@{#940926}