Group name showing on GitLab checkout page

<!---
The issue should have the following:

- The relative path of the failing spec file in the title, e.g. if the login
  test fails, include `qa/specs/ui/login/log_in_spec.rb` in the title.
  This is required so that existing issues can easily be found by searching for the spec file.
- If the issue is about multiple test failures, include the path for each failing spec file in the description.
- A link to the failing job.
- The stack trace from the job's logs in the "Stack trace" section below.
- A screenshot (if available), and HTML capture (if available), in the "Screenshot / HTML page" section below.
--->

### Summary

As per https://gitlab.com/gitlab-org/customers-gitlab-com/-/jobs/1149404630

Numerous failures on the Customers E2E Saas tests

```
Failed examples:
rspec ./spec/ui/namespace/change_namespace_spec.rb:126 # User changes plan namespace when from group to person transfers subscription
rspec ./spec/ui/purchase/purchase_group_plan_spec.rb:7 # User purchase plan for group from GitLab checkout page when upgrade from free to premium behaves like purchase plan within GitLab shows correct plan info on GitLab and CustomersDots
rspec ./spec/ui/purchase/purchase_group_plan_spec.rb:12 # User purchase plan for group from GitLab checkout page when upgrade from free to ultimate behaves like purchase plan within GitLab shows correct plan info on GitLab and CustomersDots
rspec ./spec/ui/purchase/purchase_group_plan_spec.rb:17 # User purchase plan for group from GitLab checkout page when upgrade from free with different quantity behaves like purchase plan within GitLab shows correct plan info on GitLab and CustomersDots
rspec ./spec/ui/purchase/purchase_group_plan_spec.rb:38 # User purchase plan for group from GitLab checkout page when upgrade with invalid quantity does not allow user to proceed to billing
```

### Stack trace

```
Failures:
  2) User purchase plan for group from GitLab checkout page when upgrade from free to premium behaves like purchase plan within GitLab shows correct plan info on GitLab and CustomersDots
     Failure/Error: expect(checkout).to have_subscription_details(plan, group, quantity)
       expected #has_subscription_details?({:ci_minutes=>10000, :legacy_name=>"silver", :name=>"premium", :plan_id=>"2c92c0f876e0f4cc0176e176a08f1b70", :price=>19, :rate_charge_id=>"2c92c0f876e0f4cc0176e1794ef72eea", :yearly_price=>228}, #<QA::Vendor::GitLab::Resource::Group:0x000055f5b49d9ba8 @name="test-group-fe37e7923d26", @path="test...TDOUT>>, @binmode=false, @mon_data=#<Monitor:0x000055f5b4d8fd88>, @mon_data_owner_object_id=58420>>>, 1) to return true, got false
     Shared Example Group: "purchase plan within GitLab" called from ./spec/ui/purchase/purchase_group_plan_spec.rb:7
     # ./spec/shared_examples/purchase_plan.rb:86:in `block (3 levels) in <module:QA>'
     # ./page/base.rb:62:in `initialize'
     # ./spec/shared_examples/purchase_plan.rb:83:in `new'
     # ./spec/shared_examples/purchase_plan.rb:83:in `block (2 levels) in <module:QA>'
     # /usr/local/bundle/gems/rspec-retry-0.6.2/lib/rspec/retry.rb:124:in `block in run'
     # /usr/local/bundle/gems/rspec-retry-0.6.2/lib/rspec/retry.rb:110:in `loop'
     # /usr/local/bundle/gems/rspec-retry-0.6.2/lib/rspec/retry.rb:110:in `run'
     # /usr/local/bundle/gems/rspec-retry-0.6.2/lib/rspec_ext/rspec_ext.rb:12:in `run_with_retry'
     # /usr/local/bundle/gems/rspec-retry-0.6.2/lib/rspec/retry.rb:37:in `block (2 levels) in setup'
  3) User purchase plan for group from GitLab checkout page when upgrade from free to ultimate behaves like purchase plan within GitLab shows correct plan info on GitLab and CustomersDots
     Failure/Error: expect(checkout).to have_subscription_details(plan, group, quantity)
       expected #has_subscription_details?({:ci_minutes=>50000, :legacy_name=>"gold", :name=>"ultimate", :plan_id=>"2c92c0f97700a4f70177060963d923c8", :price=>99, :rate_charge_id=>"2c92c0f97700a4f701770609640623cc", :yearly_price=>1188}, #<QA::Vendor::GitLab::Resource::Group:0x000055f5b56d4268 @name="test-group-2be9ffa2ebf5", @path="test...TDOUT>>, @binmode=false, @mon_data=#<Monitor:0x000055f5b588fb20>, @mon_data_owner_object_id=58780>>>, 1) to return true, got false
     Shared Example Group: "purchase plan within GitLab" called from ./spec/ui/purchase/purchase_group_plan_spec.rb:12
     # ./spec/shared_examples/purchase_plan.rb:86:in `block (3 levels) in <module:QA>'
     # ./page/base.rb:62:in `initialize'
     # ./spec/shared_examples/purchase_plan.rb:83:in `new'
     # ./spec/shared_examples/purchase_plan.rb:83:in `block (2 levels) in <module:QA>'
     # /usr/local/bundle/gems/rspec-retry-0.6.2/lib/rspec/retry.rb:124:in `block in run'
     # /usr/local/bundle/gems/rspec-retry-0.6.2/lib/rspec/retry.rb:110:in `loop'
     # /usr/local/bundle/gems/rspec-retry-0.6.2/lib/rspec/retry.rb:110:in `run'
     # /usr/local/bundle/gems/rspec-retry-0.6.2/lib/rspec_ext/rspec_ext.rb:12:in `run_with_retry'
     # /usr/local/bundle/gems/rspec-retry-0.6.2/lib/rspec/retry.rb:37:in `block (2 levels) in setup'
  4) User purchase plan for group from GitLab checkout page when upgrade from free with different quantity behaves like purchase plan within GitLab shows correct plan info on GitLab and CustomersDots
     Failure/Error: expect(checkout).to have_subscription_details(plan, group, quantity)
       expected #has_subscription_details?({:ci_minutes=>50000, :legacy_name=>"gold", :name=>"ultimate", :plan_id=>"2c92c0f97700a4f70177060963d923c8", :price=>99, :rate_charge_id=>"2c92c0f97700a4f701770609640623cc", :yearly_price=>1188}, #<QA::Vendor::GitLab::Resource::Group:0x000055f5b5aa3e98 @name="test-group-8592103ee741", @path="test...TDOUT>>, @binmode=false, @mon_data=#<Monitor:0x000055f5b5c21310>, @mon_data_owner_object_id=59140>>>, 20) to return true, got false
     Shared Example Group: "purchase plan within GitLab" called from ./spec/ui/purchase/purchase_group_plan_spec.rb:17
     # ./spec/shared_examples/purchase_plan.rb:86:in `block (3 levels) in <module:QA>'
     # ./page/base.rb:62:in `initialize'
     # ./spec/shared_examples/purchase_plan.rb:83:in `new'
     # ./spec/shared_examples/purchase_plan.rb:83:in `block (2 levels) in <module:QA>'
     # /usr/local/bundle/gems/rspec-retry-0.6.2/lib/rspec/retry.rb:124:in `block in run'
     # /usr/local/bundle/gems/rspec-retry-0.6.2/lib/rspec/retry.rb:110:in `loop'
     # /usr/local/bundle/gems/rspec-retry-0.6.2/lib/rspec/retry.rb:110:in `run'
     # /usr/local/bundle/gems/rspec-retry-0.6.2/lib/rspec_ext/rspec_ext.rb:12:in `run_with_retry'
     # /usr/local/bundle/gems/rspec-retry-0.6.2/lib/rspec/retry.rb:37:in `block (2 levels) in setup'
  5) User purchase plan for group from GitLab checkout page when upgrade with invalid quantity does not allow user to proceed to billing
     Failure/Error: expect(checkout.continue_to_billing_element.disabled?).to be true
       expected true
            got false
     # ./spec/ui/purchase/purchase_group_plan_spec.rb:44:in `block (4 levels) in <module:QA>'
     # ./page/base.rb:62:in `initialize'
     # ./spec/ui/purchase/purchase_group_plan_spec.rb:39:in `new'
     # ./spec/ui/purchase/purchase_group_plan_spec.rb:39:in `block (3 levels) in <module:QA>'
     # /usr/local/bundle/gems/rspec-retry-0.6.2/lib/rspec/retry.rb:124:in `block in run'
     # /usr/local/bundle/gems/rspec-retry-0.6.2/lib/rspec/retry.rb:110:in `loop'
     # /usr/local/bundle/gems/rspec-retry-0.6.2/lib/rspec/retry.rb:110:in `run'
     # /usr/local/bundle/gems/rspec-retry-0.6.2/lib/rspec_ext/rspec_ext.rb:12:in `run_with_retry'
     # /usr/local/bundle/gems/rspec-retry-0.6.2/lib/rspec/retry.rb:37:in `block (2 levels) in setup'
```

### Screenshot / HTML page

<!--
Attach the screenshot and HTML snapshot of the page from the job's artifacts:
1. Download the job's artifacts and unarchive them.
1. Open the `qa/tmp` folder.
1. Select the `.png` and `.html` files that appears in the job logs (look for `HTML screenshot: /path/to/html/page.html` / `Image screenshot: `/path/to/html/page.png`).
1. Drag and drop them here.

Note: You don't need to include a screenshot if the information it contains can be included as text. Include the text instead.
E.g., error 500/404, "Retry later" errors, etc.

If you include multiple screenshots it can be helpful to hide all but the first in a details/summary element, to avoid excessive scrolling:

<details><summary>Expand for screenshot</summary>
  drag and drop the screenshot here
</details>
-->

### Possible fixes


<!-- Base labels. -->

Story points: 2.0