🎨 Added disabled state UI for members with commenting disabled

[rob-ghost]

Why?

Staff members can now disable commenting for individual members (via the disableMemberCommenting labs flag). When a member has their commenting disabled, the comments UI needs to reflect this state appropriately.

ref https://linear.app/ghost/issue/BER-3184

What does it do?

When a member has their commenting ability disabled:

• Shows a "Commenting disabled" message with a link to contact support instead of the comment form
• Hides the reply button entirely
• Disables the like button functionality
• Hides the edit/delete menu on their own comments

The support email link uses the site's configured portal support email.

[coderabbitai]

Important

Review skipped

Draft detected.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[rob-ghost]

Future thought:

We have a few states where commenting isn't available:

1. Commenting is turned off for the publication
2. Commenting is members-only, visitor isn't a member
3. Commenting is paid-only, member is on free tier
4. Commenting is enabled but the member's ability to comment is disabled

These kind of boil down to:

• Can comment
• Can't comment (no upsell path)
• Can't comment but can be upsold

Right now the logic for determining this is spread across components. We could enumerate these as explicit states in the context (similar to how we now have isCommentingDisabled), then components just check the state rather than re-deriving it.

Something like:

type CommentingState = 'CAN_COMMENT' | 'COMMENTING_OFF' | 'NEEDS_MEMBERSHIP' | 'NEEDS_PAID_TIER' | 'MEMBER_DISABLED';