ObfuscatedFileUtil destruction should not happen on the wrong thread.

This fixes the destructor to not (incorrectly) assert that it can be
called on any thread. The class comment correctly documents that this
class has to be destroyed on the file task runner all other methods
get invoked on as well.

Change-Id: I281d9886e8076abc0f77e86a91ad7b79fb140e71
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2346931
Commit-Queue: Victor Costan <pwnall@chromium.org>
Reviewed-by: Victor Costan <pwnall@chromium.org>
Cr-Commit-Position: refs/heads/master@{#796612}

storage/browser/file_system/obfuscated_file_util.cc

@@ -291,9 +291,6 @@ ObfuscatedFileUtil::ObfuscatedFileUtil(
 }
 
 ObfuscatedFileUtil::~ObfuscatedFileUtil() {
-  // Destruction can happen on any sequence.
-  DETACH_FROM_SEQUENCE(sequence_checker_);
-
   DropDatabases();
 }