#14580871 Update: Remove subscribe actions for unverfied email users

Proposed Changes

• This PR updates the buttons that let users subscribe to sites but send them an error message asking them to verify the emails first.

See

Screenshot for translators.

Why are these changes being made?

The changes are that we check the subscribe buttons and other buttons and send a notice instead.

Testing Instructions

Create a new unverfied email user.

Go to /read
Notice that you can’t subscribe to a site or follow a conversation.

Go to /read/subscriptions
Notice that you can’t follow or subscribe to a site.
The UI elements are not even there.

Use a regual user
Notice that when you go to /read and /read/subscritions the UI elements are there so you can follow and subscribe to the site.

Pre-merge Checklist

• Has the general commit checklist been followed? (PCYsg-hS-p2)
• 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)?
• For changes affecting Jetpack: Have we added the “[Status] Needs Privacy Updates” label if this pull request changes what data or activity we track or use (p4TIVU-aUh-p2)?