Improve user flow when he wants to re-encrypt a previously imported seed phrase (with lost password)

[jrainville]

Currently, if a user want to re-import a seed phrase for an account already imported, in the case of a lost password for example, he cannot, because the DB already exists. The suggested behaviour now is to delete and re-install the app, which is annoying.

My suggestion is to add a new status-go endpoint that forces the deletion of the previous DB with the wanted seed phrase.

This would be shown after the the first original warning would be show. Instead of saying that he should uninstall the app though, we tell him that if he's sure, like very sure, he can instead overwrite the previous DB and create a new one, with a new button.

This issue depends on this other issue: #5029

[iurimatias]

easier to do after #9807