Fix for ENG-11036 and other issues.

• Used LogInHandler to exclusively navigate to backup progress and error screens, based on Redux state.
• Updated LogInHandler triggers (useRef change logic) to track not only loggedIn state but also restoration states.
• Removed other places where these screens were navigated from

Depends on D15171

• Previous behavior:
  • Logout navigates to LoggedOutModal as before, and clears all logged-in screens (LogOutActionType)
  • LogIn action when restoration finished works the same - clears all "account modals" and displays logged in nav tree
• New "state hash" - verified that LogInHandler logic is triggered only when one of hashed states changes
• Primary restoration
  • progress screen is displayed
  • on failure, error screen is displayed
  • on success, log in action is triggered
  • after killing and reopening during UserData restore, the restore progress screen is displayed (both dev and non-dev build - nav state handling is a bit different)
  • after killing and reopening after failure, user data restore handler is triggered and navigation between restore progress <-> error screens happens based on Redux state
• QR login - the same as Primary restoration, with the difference that initially QR progress screen is displayed (same as previous behavior, this screen is navigated directly without LogInHandler - condition inside the handler covers this case)