[PM-10570] Ensuring strategy exists before doing "in" check. Fixes "TypeError: C…

[mcalmus]

When session times out and "send verification code email again" link is clicked, the following error occurs and no feedback is given to user.

TypeError: Cannot use 'in' operator to search for 'email$' in null

This change ensure strategy object exists before calling "in".

🎟️ Tracking

📔 Objective

📸 Screenshots

⏰ Reminders before review

• Contributor guidelines followed
• All formatters and local linters executed and passed
• Written new unit and / or integration tests where applicable
• Protected functional changes with optionality (feature flags)
• Used internationalization (i18n) for all UI strings
• CI builds passed
• Communicated to DevOps any deployment requirements
• Updated any necessary documentation (Confluence, contributing docs) or informed the documentation team

🦮 Reviewer guidelines

• 👍 (:+1:) or similar for great changes
• 📝 (:memo:) or ℹ️ (:information_source:) for notes or general info
• ❓ (:question:) for questions
• 🤔 (:thinking:) or 💭 (:thought_balloon:) for more open inquiry that's not quite a confirmed issue and could potentially benefit from discussion
• 🎨 (:art:) for suggestions / improvements
• ❌ (:x:) or ⚠️ (:warning:) for more significant problems or concerns needing attention
• 🌱 (:seedling:) or ♻️ (:recycle:) for future improvements or indications of technical debt
• ⛏ (:pick:) for minor or nitpick changes

[CLAassistant]

All committers have signed the CLA.

[bitwarden-bot]

Thank you for your contribution! We've added this to our internal Community PR board for review.
ID: PM-10570

[mcalmus]

@rr-bw Could I please get a review?

[trmartin4]

Thank you for reaching out. We are currently reviewing the change in accordance with our Contribution Review Process. We need to assess how the change impacts other internal initiatives or other work in that particular area of the codebase. We hope you understand, and we appreciate your patience.

[trmartin4]

Hello @mcalmus.

Thank you for your contribution. After reviewing internally, we have noted that this change has been implemented as part of #12811, in which we addressed the type issues that you also identified as part of internal efforts to respect the TS strict flag.