Tentatively delete the sqlite3_initialize suppression. The race should've been fixed in r212984

tools/valgrind/tsan/suppressions.txt

 # There are a few kinds of suppressions in this file.
 # 1. third party stuff we have no control over
 #
 # 2. intentional unit test errors, or stuff that is somehow a false positive
 # in our own code, or stuff that is so trivial it's not worth fixing
 #
 # 3. Suppressions for real chromium bugs that are not yet fixed.
 # These should all be in chromium's bug tracking system (but a few aren't yet).
 # Periodically we should sweep this file and the bug tracker clean by
 # running overnight and removing outdated bugs/suppressions.
@@ skipping 148 matching lines @@
 }
 
 {
   Two writes, same value (under sqlite3Malloc)
   ThreadSanitizer:Race
   ...
   fun:sqlite3Malloc*
 }
 
 {
-  Two writes, same value (sqlite3_initialize)
-  ThreadSanitizer:Race
-  fun:sqlite3_initialize
-  fun:openDatabase
-}
-
-{
   bug_84094_a  (Could be benign. See bug for details)
   ThreadSanitizer:Race
   ...
   fun:pcache1Fetch
   fun:sqlite3PcacheFetch
 }
 
 {
   bug_84094_b (Could be benign. See bug for details)
   ThreadSanitizer:Race
@@ skipping 943 matching lines @@
 }
 {
   bug_268924
   ThreadSanitizer:Race
   fun:base::PowerMonitor::PowerMonitor
   fun:content::ChildThread::Init
   fun:content::ChildThread::ChildThread
   fun:content::UtilityThreadImpl::UtilityThreadImpl
   fun:content::UtilityMainThread::InitInternal
 }