Show plans for all user groups in the marketing cookie

What does this MR do and why?

What?

Show plans for all user groups in the marketing cookie

• all levels of access desired now so we'll open it up to all groups where a member is part of...directly.
• see gitlab-com/marketing/digital-experience/buyer-experience#3762 (closed)

Why?

All users: We introduce the cookie to all users of groups, whether or not they can up-tier their own GitLab namespaces. This means that the gitlab_tier cookie for a user will show you which tiers a user is a part of.

• Opportunity: We have a wider net of users, meaning more users will see more of the premium/ultimate specific messaging when navigating across pages. Users could talk to their group owners about why they should up-tier, which could be valuable. 
• Risk:  Could adding a purchase flow that doesn’t exist be confusing to users? How can we measure this?

Related to gitlab-com/marketing/digital-experience/buyer-experience#3762 (closed)

• db analysis: !155881 (comment 1943395855)

MR acceptance checklist

Please evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.

Screenshots or screen recordings

Screenshots are required for UI changes, and strongly recommended for all other merge requests.

Before	After

How to set up and validate locally

Numbered steps to set up and validate the change are strongly suggested.

Related to #464365