#7605795 Launchpad: Email Validation Banner

Testing Instructions

This PR is for adding an email validation banner on the Launchpad page. The banners shows up for any new user that hasn’t validated their email yet.

1. Create a new WordPress account. (You can use Temp Email)
2. Create a new Launchpad site
3. Go to http://calypso.localhost:3000/setup/launchpad?flow=link-in-bio&siteSlug=YOUR_SITE_SLUG
4. You should see the banner displayed on the top of the page
5. Click Resend Email. You should see the success email notice appear in the top-right and you should receive a new email
6. Click change email address. You should be redirected to your account page. Click Resend Email. You should see the success email notice appear in the top-right and you should receive a new email
7. Go back to Launchpad
8. Use the DevTools to block the request URL for the email verification. By doing this you can simulate a failed request. Click Resend Email. You should see the failure email notice appear in the top-right and you should not receive a new email
9. Click change email address. You should be redirected to your account page. Click Resend Email. You should see the failure email notice appear in the top-right and you should not receive a new email
10. Go back to Launchpad
11. Close the email verification banner and refresh the page. The banner should appear again.
12. Go to your email and follow the verification link. Once you have verified your email, go back to Launchpad. You should not see the email banner anymore

Icon Changes

After a conversation in slack, I am going for an already existing icon as opposed to the custom icon in the mockup. We will most likely follow up on this

Pre-merge Checklist

• Have you written new tests for your changes?
• Have you tested the feature in Simple (P9HQHe-k8-p2), Atomic (P9HQHe-jW-p2), and self-hosted Jetpack sites (PCYsg-g6b-p2)?
• Have you checked for TypeScript, React or other console errors?
• Have you used memoizing on expensive computations? More info in Memoizing with create-selector and Using memoizing selectors and Our Approach to Data
• Have we added the “[Status] String Freeze” label as soon as any new strings were ready for translation (p4TIVU-5Jq-p2)?

Related to #68961