Remove workaround for cetcompat linker problem

Tested on hardware as part of
https://chromium-review.googlesource.com/c/chromium/src/+/2494509/2/build/config/compiler/BUILD.gn

Bug: 1136664
Change-Id: I7c5cf2c54259c6aa29fd1ea39a66cf3e8ae7ac4c
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2541782Reviewed-by: Vitaly Buka <vitalybuka@chromium.org>
Reviewed-by: Dirk Pranke <dpranke@google.com>
Commit-Queue: Alex Gough <ajgo@chromium.org>
Cr-Commit-Position: refs/heads/master@{#828422}

build/config/compiler/BUILD.gn

@@ -2266,13 +2266,6 @@ config("win_pdbaltpath") {
   # build reproducibility. Debuggers look for pdb files next to executables,
   # so there's no downside to always using this.
   ldflags = [ "/pdbaltpath:%_PDB%" ]
-
-  if (enable_cet_shadow_stack && use_lld) {
-    # TODO(crbug.com/1136664): Investigate why Windows does not recognize
-    # CET in some binaries linked by LLD with /DEBUG.
-    # This is the best place for work around as it follows all /DEBUG uses.
-    ldflags += [ "/DEBUG:NONE" ]
-  }
 }
 
 # Full symbols.