GitLab

* Removed bulk_leak_check_controller_android classes, as they were part of the temporary API for the password check and never actually got used
* Used an instance of the PasswordCheck class to manage the lifecycle of the password check in Safety check
* Changed the initialization logic to account for the asynchronous availability of the # of saved and compromised passwords
* Added logic to block displaying successful states without compromises on fetching the data from disk (# of saved and compromised passwords)
* Added unit tests to verify various asynchronous timing scenarios

Bug: 1070620
Change-Id: Ia4aee1b06ba820f551a4f66c923174d20b5f8007
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2336078Reviewed-by: Natalie Chouinard <chouinard@chromium.org>
Reviewed-by: Friedrich [CET] <fhorschig@chromium.org>
Commit-Queue: Andrey Zaytsev <andzaytsev@google.com>
Cr-Commit-Position: refs/heads/master@{#795836}