[Passwords] Don't do password leak check if it can't be muted

The filed bug report contained several problems:

1) Password leak check ignored broken `PasswordStore`. `PasswordStore`
stored if any leak notification was already shown to the user and
allowed to show the leak notification at most once. Since
`PasswordStore` was broken, the user was prompted with
password leak every time they login to the website.

2) If the saving was disabled, form manager was not cleared and this
meant that every website navigation was form submission.

This lead to Password Manager prompting leaked password dialog on
every navigation.

Move password leak check after checking that password store is
available for write and clear the submitted form even if saving is
disabled.

(cherry picked from commit 01f4347a31d0cabfe12e00717f757c64c5d49aa7)

Bug: b/327621222
Change-Id: Ic43c34f33b0315ae645affee3b5398ecc221007a
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5317876
Reviewed-by: Vasilii Sukhanov <vasilii@chromium.org>
Commit-Queue: Din Nezametdinov <shaikhitdin@google.com>
Cr-Original-Commit-Position: refs/heads/main@{#1264635}
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5340376
Auto-Submit: Din Nezametdinov <shaikhitdin@google.com>
Commit-Queue: Vasilii Sukhanov <vasilii@chromium.org>
Cr-Commit-Position: refs/branch-heads/6312@{#387}
Cr-Branched-From: 6711dcdae48edaf98cbc6964f90fac85b7d9986e-refs/heads/main@{#1262506}

• components/password_manager/core/browser/password_manager.cc[diff]
• components/password_manager/core/browser/password_manager_unittest.cc[diff]