Re-evaluate our use of "subscription is in read-only mode" in reseller customer messaging

Problem

It has been brought up that the wording your subscription is in read-only mode might be confusing to the customers, leading them to think that their instance or namespace is in read-only mode. Customers might also be confused about why it's read-only.

@esybrant provided the following reasoning for keeping the current wording:

There are a few reasons that we chose this particular messaging:

1. We've used similar messaging for other situations where customers can't make changes to their subscription, and we haven't gotten feedback that users are confused.
2. The context is really important here--The user only sees this message when they are trying to make a subscription change (when they're clicking on a button trying to add seats or buy additional products). So this isn't a generic message about read-only mode on the top-level group page, it is contextual to a subscription change, which is important to user understanding.
3. The rest of the message explains more about a read-only subscription and how to make changes to it.

Proposal

Investigate whether we need to change this wording based on customer feedback. We are not actively gathering this feedback, but it's something we can get via:

1. Support team sharing support tickets where customer brought this up.
2. Survey or interview reseller customers.

Might also consider explaining why it's read-only.

Result

Next steps (if any)

How will we measure success?