win: Disable CFG in release component builds for a bit.

After the 2nd-to-last clang roll, release component builds make
chrome crash on launch due to CFG. Disable CFG for component builds
until we roll in a fix.

This does not affect shipping chrome, which doesn't use component builds.
CFG was already disabled in debug component builds.

Bug: 1147194,1147445
Change-Id: Idd2ab6dcc6e89e604d8f0c6f37369f7b389b31c0
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2532875
Commit-Queue: Nico Weber <thakis@chromium.org>
Auto-Submit: Nico Weber <thakis@chromium.org>
Reviewed-by: Hans Wennborg <hans@chromium.org>
Cr-Commit-Position: refs/heads/master@{#826317}

build/config/win/BUILD.gn

@@ -354,7 +354,9 @@ config("cfi_linker") {
   # ASan and CFG leads to slow process startup. Chromium's test runner uses
   # lots of child processes, so this means things are really slow. Disable CFG
   # for now. https://crbug.com/846966
-  if (!is_debug && !is_asan) {
+  # TODO(thakis): Re-enable in release component builds once they work again,
+  # https://crbug.com/1147194
+  if (!is_debug && !is_asan && !is_component_build) {
     # Turn on CFG bitmap generation and CFG load config.
     if (target_cpu == "arm64") {
       # longjmp protection is temporarily disabled on Windows on Arm64 due to