Reset the ChromeOSTokenManager between tests, to fix a large number of
flaky tests caused by a DCHECK in
ChromeOSTokenManager::IsTPMTokenEnabled. This DCHECK was caused by
|thread_checker_| detecting that the ChromeOSTokenManager was
accessed from different Browser IO Threads, from different unit tests.
Bug: 1267412
Change-Id: I8a56ef271dcd6d209d757b0671578d91b2cf0dff
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3265252
Reviewed-by: Lei Zhang <thestig@chromium.org>
Reviewed-by: Matt Mueller <mattm@chromium.org>
Reviewed-by: David Benjamin <davidben@chromium.org>
Reviewed-by: Michael Ershov <miersh@google.com>
Commit-Queue: David Bienvenu <davidbienvenu@chromium.org>
Cr-Commit-Position: refs/heads/main@{#942803}
aec6d7e129