Roll out of zuora_hpm_no_refresh

<!-- Title suggestion: [Feature flag] Enable description of feature -->

# Summary

<!-- Short description of what the feature is about and link to relevant other issues. -->

This issue is to rollout [Static Zuora component](https://gitlab.com/gitlab-org/customers-gitlab-com/-/merge_requests/4553) on CustomersDot production,
that is currently behind the [`zuora_hpm_no_refresh`](https://gitlab.com/gitlab-org/customers-gitlab-com/-/feature_flags/126/edit) feature flag.

## Owners

- Team: ~"group::purchase" 
- Most appropriate Slack channel to reach out to: [#g_purchase](https://gitlab.slack.com/archives/C01BPTAP599)
- Best individual to reach out to: @agulina or @lmeckley 
- PM: @tgolubeva 

## The Rollout Plan

- Partial Rollout with specific Customers on CustomersDot, [via Unleash](https://docs.gitlab.com/ee/operations/feature_flags.html#user-ids)
- Rollout on CustomersDot for a certain period (How long)
- Percentage Rollout on CustomersDot
- Rollout Feature for everyone as soon as it's ready

<!-- Which dashboards from https://dashboards.gitlab.net are most relevant? Sentry errors reports can also be useful to review -->

## Expectations

### What are we expecting to happen?

The payment forms in CDot should use the new Zuora component but functionally behave the same as the old implementation in the happy path. The only difference is that errors will not cause the iframe to re-render.

### What might happen if this goes wrong?

All CDot payment pages could be impacted and users could be preventing from making payments, renewing, etc. The iframe could also potentially not load. 

### What can we monitor to detect problems with this?

<!-- Which dashboards from https://dashboards.gitlab.net are most relevant? -->

## Rollout Steps

### Rollout on non-production environments

- [ ] Ensure that the feature MRs have been deployed to non-production environments, i.e. `customers-staging`.
- [ ] Consider announcing that the flag will be enabled to potentially impacted groups, e.g. `#s_fulfillment_engineering`
- [ ] Enable the feature globally on non-production environments by applying the appropriate environment, e.g. `customers-staging` and `customers-development`.
- [ ] Verify that the feature works as expected. Posting the QA result in this issue is preferable.

### Preparation before production rollout

- [ ] Ensure that the feature MRs have been deployed to production
- [ ] Check if the feature flag change needs to be accompanied with a
  [change management issue](https://about.gitlab.com/handbook/engineering/infrastructure/change-management/#feature-flags-and-the-change-management-process).
  Cross link the issue here if it does.
- [ ] Ensure that you or a representative in Fulfillment can be available for at least 2 hours after feature flag updates in production.
  If a different developer will be covering, or an exception is needed, please inform the Fulfillment team in #s_fulfillment_engineering
- [ ] Ensure any documentation has been updated
- [ ] Announce on [the feature issue](ISSUE LINK) an estimated time this will be enabled on production if applicable
- [ ] If the feature might impact the user experience, notify `#s_fulfillment` and potentially `#support_gitlab-com`, as well as your team channel ([more guidance when this is necessary in the dev docs](https://docs.gitlab.com/ee/development/feature_flags/controls.html#communicate-the-change)).

### Global rollout on CustomersDot production

- [ ] Confirm the feature flag is enabled on `staging` without incident
- [ ] Roll out the feature to targeted testing users first (if applicable)
- [ ] If applicable, [incrementally roll out](https://docs.gitlab.com/ee/operations/feature_flags.html#percent-rollout) the feature.
- [ ] Verify the change has the desired outcome with the limited rollout before enabling the feature globally on production.
- [ ] Enable the feature globally on production environment 
- [ ] Announce on [the feature issue](ISSUE LINK) that the feature has been globally enabled.
- [ ] Wait for [at least one day for the verification term](https://about.gitlab.com/handbook/product-development-flow/feature-flag-lifecycle/#including-a-feature-behind-feature-flag-in-the-final-release).

### Release the feature

After the feature has been [deemed stable](https://about.gitlab.com/handbook/product-development-flow/feature-flag-lifecycle/#including-a-feature-behind-feature-flag-in-the-final-release),
the clean up should be done as soon as possible to permanently enable the feature and reduce complexity in the codebase.

<!-- The checklist here is to help stakeholders keep track of the feature flag status -->
- [ ] Create a merge request to remove `<feature-flag-name>` feature flag
  - [ ] Remove all references to the feature flag from the codebase
- [ ] Ensure that the cleanup MR has been deployed to both staging and production
- [ ] Disable the feature flag via the [CustomersDot dashboard](https://gitlab.com/gitlab-org/customers-gitlab-com/-/feature_flags)
- [ ] Ensure production environment is still working as expected
- [ ] Remove the Unleash feature flag from the [CustomersDot dashboard](https://gitlab.com/gitlab-org/customers-gitlab-com/-/feature_flags)
- [ ] Close this rollout issue.

## Rollback Steps

- [ ] This feature can be disabled by performing the following actions:
  - [ ] Disable the Unleash flag on the [feature flag page](LINK TO THE FEATURE FLAG EDIT PAGE)

Story points: 2.0