Don't include sanitizer options for libc++

It breaks component builds since libc++ doesn't actually depend on
these sources. The executable including these symbols should be enough
for them to correctly override ASAN's weak definitions.

Bug: 1321148
Change-Id: I945ebd0853cc9946763becaa3997ff9b021ca433
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3621985
Reviewed-by: Nico Weber <thakis@chromium.org>
Auto-Submit: Leonard Grey <lgrey@chromium.org>
Commit-Queue: Leonard Grey <lgrey@chromium.org>
Cr-Commit-Position: refs/heads/main@{#999442}
NOKEYCHECK=True
GitOrigin-RevId: 8f4efeed1099840dc13d05e8be0887082979f99f
diff --git a/third_party/libc++/BUILD.gn b/third_party/libc++/BUILD.gn
index 045a5ef..74b6ad6 100644
--- a/third_party/libc++/BUILD.gn
+++ b/third_party/libc++/BUILD.gn
@@ -145,10 +145,6 @@
     "//build/config/compiler:rtti",
   ]
 
-  if (using_sanitizer) {
-    configs += [ "//build/config/sanitizers:sanitizer_options_link_helper" ]
-  }
-
   if (libcxx_is_shared && !is_win) {
     configs -= [ "//build/config/gcc:symbol_visibility_hidden" ]
     configs += [ "//build/config/gcc:symbol_visibility_default" ]