Speculatively some old sqlite suppressions

ClusterFuzz claims this is since fixed, but in that case the
suppression should have been removed.

Bug: 84094
Change-Id: I316f6c97f99fa49224297050d9c3385b29bac0ef
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1661473
Commit-Queue: Victor Costan <pwnall@chromium.org>
Auto-Submit: David Benjamin <davidben@chromium.org>
Reviewed-by: Victor Costan <pwnall@chromium.org>
Cr-Original-Commit-Position: refs/heads/master@{#669742}
Cr-Mirrored-From: https://chromium.googlesource.com/chromium/src
Cr-Mirrored-Commit: 10441c0c39a10cdd0570c456a793327c0e84657c

sanitizers/tsan_suppressions.cc

@@ -34,11 +34,6 @@ char kTSanDefaultSuppressions[] =
     // [test-only]. http://crbug.com/927330.
     "race:content/browser/net_info_browsertest.cc\n"
 
-    // http://crbug.com/84094.
-    "race:sqlite3StatusSet\n"
-    "race:pcache1EnforceMaxPage\n"
-    "race:pcache1AllocPage\n"
-
     // http://crbug.com/120808
     "race:base/threading/watchdog.cc\n"