Don't update paint invalidation container in CAP

Paint invalidation container information is no available in CAP, as it
requires querying the compositing state to see whether a GraphicsLayer
is created in a PaintLayer's ancestor chain.

UpdatePaintInvalidationContainer should therefore be a no-op in CAP.
This is an incremental change in pursuit of adding a DCHECK(!CAP) in
LayoutObject::EnclosingCompositedContainer and removing that
DisableCompositingQueryAssert from CAP codepaths.

Bug: 1007989
Change-Id: I0ecd12fdf907f1746d54a67437143cb5ce7eb5fa
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2118212
Reviewed-by: Xianzhu Wang <wangxianzhu@chromium.org>
Commit-Queue: Xianzhu Wang <wangxianzhu@chromium.org>
Cr-Commit-Position: refs/heads/master@{#753061}

third_party/blink/renderer/core/paint/paint_invalidator.cc

@@ -172,6 +172,9 @@ void PaintInvalidator::UpdatePaintingLayer(const LayoutObject& object,
 void PaintInvalidator::UpdatePaintInvalidationContainer(
     const LayoutObject& object,
     PaintInvalidatorContext& context) {
+  if (RuntimeEnabledFeatures::CompositeAfterPaintEnabled())
+    return;
+
   if (object.IsPaintInvalidationContainer()) {
     context.paint_invalidation_container = ToLayoutBoxModelObject(&object);
     if (object.StyleRef().IsStackingContext() || object.IsSVGRoot())