Paid Content Block: Before Stripe Connection, Block Partially Renders in Subscription Emails

### Impacted plugin

Jetpack

### Quick summary

When an email is sent out for a post that has a Paid Content Block before a user has connected a Stripe account the behavior is confusing.

We include the text:

> Connect to Stripe to use this block on your site. Connect

But only site owners can take that action. Additionally, we show the contents of the post and a message.

### Steps to reproduce

1. Add a paid content block
2. Don't connect Stripe
3. Publish the post

### A clear and concise description of what you expected to happen.

The block indicates this will be disabled until a Stripe connection:


As a result, I wouldn't expect we would send out the subscriber-only content.

Also, we shouldn't show the Stripe connection notice to all subscribers.

### What actually happened

The email sent includes the subscriber-only content and a notice to connect Stripe:


### Impact

Most (> 50%)

### Available workarounds?

No but the platform is still usable

### Platform (Simple and/or Atomic)

Self-hosted

### Logs or notes

_No response_

The report names no files, tests, or entry points. Reproduce the issue with an unconnected Stripe account, a Paid Content Block, and a published post, then trace how the block is rendered in subscription emails. Done means subscriber-only content and the Stripe connection notice are not sent to subscribers before connection.

Written by the indexing model from the issue text.