[High5] Fix CryptohomeRecoverySetupScreenTest

CryptohomeRecoverySetupScreenTest was previously doing too many hacks in
order to properly show the CryptohomeRecoverySetupScreen. It would go
through the whole OOBE flow once and force it to stop after the last
screen so that it could show the CryptohomeRecoverySetupScreen. Thus the
screen was actually being shown twice. With this change, the OOBE flow
will be stopped exactly where this screen needs to be tested, without
needing extra steps such as copying the original UserContext. The fact
that the screen was being shown twice was causing some new logic in
WizardController to trigger a CHECK in a codepath for the new PIN-only
OOBE that is being developed.

Bug: b/365059362, b/372853725, b/348326316
Change-Id: I3b5eebbe8778aa4bced242c35442bc27818a51a3
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5923501
Commit-Queue: Hardik Goyal <hardikgoyal@chromium.org>
Reviewed-by: Hardik Goyal <hardikgoyal@chromium.org>
Auto-Submit: Renato Silva <rrsilva@google.com>
Cr-Commit-Position: refs/heads/main@{#1367827}