fixes for switching accounts on push notifications

[zoom-ua]

@chrisnojima @mmaxim

• Spurious account switches on background push: Silent/background notifications were triggering account switches. Fixed by checking userInteraction before switching — only a user tap should initiate a switch.
• Wrong-account badge updates on Android: Badge count from FCM payload was applied immediately before validating which account the push was for. Moved badge application to after Go confirms the targetUID matches the active account.
• Push for different account crashing/logging incorrectly on Android: Added targetUID parameter to HandleBackgroundNotification in Go; Android now passes the UID and Go rejects early with a distinct error, which Kotlin logs as info rather than an error.
• Pending push lost during account switch store reset: When switching accounts, Z.resetAllStores() was clearing the pending push notification. Now it's preserved across the reset and restored afterward.
• Login errors leaving userSwitching flag stuck + stale pending push: On login failure, userSwitching was turned off but the pending push notification wasn't cleared. Now both are cleaned up together.
• Push for different account arriving before configuredAccounts loads: Previously silently dropped. Now saved as pending and replayed once the account list is available.
• OnLogin not clearing the multiple-accounts cache: Only logout cleared the cache, so a new login wouldn't reflect the updated account count until the next notification. Added OnLogin hook to clear it on both transitions.