giseldo/neodataset huggingface dataset:
Add storage product details section in subscription-v2 component

<!-- Please complete the template below as best as you can. Make sure to check if this issue has already been raised by someone else first to avoid duplication. 

For each section below, please add screenshots or links or anything that may help visual learners understand the problem better, even if this takes you an extra minute or two this is a great help to some folks.

https://www.learning-styles-online.com/style/visual-spatial/

-->
### Proposal
Similar to https://gitlab.com/gitlab-org/customers-gitlab-com/-/issues/5379, create a new section to show storage product details.  
![image](/uploads/0639894b42be02fbd4652fb6434c17f5/image.png)

<!-- Consult with `@gitlab-com/business-technology/enterprise-apps/zuora-architects` on the ~"Enterprise Applications" team if Zuora business logic is involved. -->

### Result

### Next steps (if any)

### How will we measure success?

Design: https://gitlab.com/gitlab-org/customers-gitlab-com/-/issues/3916

Story points: 2.0
Add main product details section in subscription-v2 component

<!-- Please complete the template below as best as you can. Make sure to check if this issue has already been raised by someone else first to avoid duplication. 

For each section below, please add screenshots or links or anything that may help visual learners understand the problem better, even if this takes you an extra minute or two this is a great help to some folks.

https://www.learning-styles-online.com/style/visual-spatial/

-->
### Proposal
Add the section to show main product details in the `subscription-v2` component that will be created in https://gitlab.com/gitlab-org/customers-gitlab-com/-/issues/5376. This section will be used to display the main product details only (and not addon products like CI mins and storage since they have a slightly different UI).
![image](/uploads/09e1d83139f1ffbdc4556de0fbb3093e/image.png)

Design: https://gitlab.com/gitlab-org/customers-gitlab-com/-/issues/3916

<!-- Consult with `@gitlab-com/business-technology/enterprise-apps/zuora-architects` on the ~"Enterprise Applications" team if Zuora business logic is involved. -->

### Result

### Next steps (if any)

### How will we measure success?

Story points: 2.0
Add subscription level details to new subscription card for ramp subscriptions

<!-- Please complete the template below as best as you can. Make sure to check if this issue has already been raised by someone else first to avoid duplication. 

For each section below, please add screenshots or links or anything that may help visual learners understand the problem better, even if this takes you an extra minute or two this is a great help to some folks.

https://www.learning-styles-online.com/style/visual-spatial/

-->
### Proposal
Add subscription level details section as per the [new designs](https://gitlab.com/gitlab-org/customers-gitlab-com/-/issues/3916/) for the subscription card for ramp subscriptions.  
Note: The side menu bar to modify the subscription is out of scope of this issue and will be tackled in a separate issue.
![image](/uploads/07b664d40eb1063bb68cc441307fa8c9/image.png)

The new component should be behind the `display_ramp_subscriptions` feature flag which will be added in https://gitlab.com/gitlab-org/customers-gitlab-com/-/issues/5373.

<!-- Consult with `@gitlab-com/business-technology/enterprise-apps/zuora-architects` on the ~"Enterprise Applications" team if Zuora business logic is involved. -->

### Result

### Next steps (if any)
| Task | MR | Status |
| ------ | ------ |------ |
|   Introduce card & storybook     | https://gitlab.com/gitlab-org/customers-gitlab-com/-/merge_requests/6244       | ~"workflow::complete"    | 
| Tooltip content | https://gitlab.com/gitlab-org/customers-gitlab-com/-/merge_requests/6269 | ~"workflow::complete" 
|    UI tweaks    |    https://gitlab.com/gitlab-org/customers-gitlab-com/-/merge_requests/6318    | ~"workflow::complete" | 
### How will we measure success?

**Design:** https://gitlab.com/gitlab-org/customers-gitlab-com/-/issues/3916/ and https://www.figma.com/file/U9JvYVy1Ls9IKrrPw1vt38/Subscription-management?node-id=239%3A10609&t=RFsPIuAGNurLWCJB-0

Story points: 3.0
Add ramp details in SubscriptionPresenter

<!-- Please complete the template below as best as you can. Make sure to check if this issue has already been raised by someone else first to avoid duplication. 

For each section below, please add screenshots or links or anything that may help visual learners understand the problem better, even if this takes you an extra minute or two this is a great help to some folks.

https://www.learning-styles-online.com/style/visual-spatial/

-->

### Problem
Currently the ramp details are not sent to the frontend under the products.  
![image](/uploads/ea5af87826e42aaecbf911d30d707916/image.png)

### Proposal
Add a new attribute `ramps` for each subscription in `subscription_presenter.rb` which will return the list of ramps in that subscription. Details needed in every ramp are - 
1. Start date
2. End Date
3. Quantity
4. Price per unit
5. Product Name
6. Rate Plan Id

<!-- Consult with `@gitlab-com/business-technology/enterprise-apps/zuora-architects` on the ~"Enterprise Applications" team if Zuora business logic is involved. -->

### Result

### Next steps (if any)

### How will we measure success?

Story points: 3.0
Add `is_ramp_subscription` flag in SubscriptionPresenter

<!-- Please complete the template below as best as you can. Make sure to check if this issue has already been raised by someone else first to avoid duplication. 

For each section below, please add screenshots or links or anything that may help visual learners understand the problem better, even if this takes you an extra minute or two this is a great help to some folks.

https://www.learning-styles-online.com/style/visual-spatial/

-->

### Proposal
Add `is_ramp_subscription` flag in `subscription_presenter.rb` which can be used on the frontend to identify whether the subscription is a ramp subscription. 


<!-- Consult with `@gitlab-com/business-technology/enterprise-apps/zuora-architects` on the ~"Enterprise Applications" team if Zuora business logic is involved. -->

### Result

### Next steps (if any)

### How will we measure success?

Story points: 1.0
[Feature flag] Create new feature flag `display_ramp_subscriptions`

<!-- Please complete the template below as best as you can. Make sure to check if this issue has already been raised by someone else first to avoid duplication. 

For each section below, please add screenshots or links or anything that may help visual learners understand the problem better, even if this takes you an extra minute or two this is a great help to some folks.

https://www.learning-styles-online.com/style/visual-spatial/

-->

### Problem
Create a [new feature flag](https://gitlab.com/gitlab-org/customers-gitlab-com/-/feature_flags) `display_ramp_subscriptions` which can be used to control the display of the [new card design](https://gitlab.com/gitlab-org/customers-gitlab-com/-/issues/3916/) for ramp subscriptions.  

Rollout issue: https://gitlab.com/gitlab-org/customers-gitlab-com/-/issues/5385

### Proposal

<!-- Consult with `@gitlab-com/business-technology/enterprise-apps/zuora-architects` on the ~"Enterprise Applications" team if Zuora business logic is involved. -->

### Result

### Next steps (if any)

### How will we measure success?

Story points: 1.0
[FF cleanup] Subscription update Preview: use_orders_api_to_preview_amendment

### Problem

The scope of this issue is to perform cleanup tasks for FF `use_orders_api_to_preview_amendment` ([original rollout issue](https://gitlab.com/gitlab-org/customers-gitlab-com/-/issues/4774)).

### Proposal

Perform `Release the feature` tasks:

* [ ] 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 issue.

Story points: 1.0
[FF cleanup] Subscription upgrade Preview: use_orders_api_to_preview_upgrade

### Problem

The scope of this issue is to perform cleanup tasks for FF `use_orders_api_to_preview_upgrade` ([original rollout issue](https://gitlab.com/gitlab-org/customers-gitlab-com/-/issues/5051)).

### Proposal

Perform `Release the feature` tasks:

* [x] Create a merge request to remove `<feature-flag-name>` feature flag
  * [x] Remove all references to the feature flag from the codebase
* [x] Ensure that the cleanup MR has been deployed to both staging and production
* [x] Disable the feature flag via the [CustomersDot dashboard](https://gitlab.com/gitlab-org/customers-gitlab-com/-/feature_flags)
* [x] Ensure production environment is still working as expected
* [x] Remove the Unleash feature flag from the [CustomersDot dashboard](https://gitlab.com/gitlab-org/customers-gitlab-com/-/feature_flags)
* [x] Close this issue.

Story points: 1.0
[FF cleanup] Reconciliation: use_orders_api_reconciliation_workflow

### Problem

The scope of this issue is to perform cleanup tasks for FF `use_orders_api_reconciliation_workflow` [QSR original rollout issue](https://gitlab.com/gitlab-org/customers-gitlab-com/-/issues/5066)).

### Proposal

Perform `Release the feature` tasks:

* [x] Create a merge request to remove `<feature-flag-name>` feature flag
  * [x] Remove all references to the feature flag from the codebase
* [x] Ensure that the cleanup MR has been deployed to both staging and production
* [x] Disable the feature flag via the [CustomersDot dashboard](https://gitlab.com/gitlab-org/customers-gitlab-com/-/feature_flags)
* [x] Ensure production environment is still working as expected
* [x] Remove the Unleash feature flag from the [CustomersDot dashboard](https://gitlab.com/gitlab-org/customers-gitlab-com/-/feature_flags)
* [x] Close this issue.

Story points: 1.0
[FF cleanup] Auto renewal: use_orders_api_auto_renew_workflow

### Problem

The scope of this issue is to perform cleanup tasks for FF `use_orders_api_auto_renew_workflow` ([AR original rollout issue](https://gitlab.com/gitlab-org/customers-gitlab-com/-/issues/5064).

### Proposal

Perform `Release the feature` tasks:

* [x] Create a merge request to remove `<feature-flag-name>` feature flag
  * [x] Remove all references to the feature flag from the codebase
* [x] Ensure that the cleanup MR has been deployed to both staging and production
* [x] Disable the feature flag via the [CustomersDot dashboard](https://gitlab.com/gitlab-org/customers-gitlab-com/-/feature_flags)
* [x] Ensure production environment is still working as expected
* [x] Remove the Unleash feature flag from the [CustomersDot dashboard](https://gitlab.com/gitlab-org/customers-gitlab-com/-/feature_flags)
* [x] Close this issue.

Story points: 1.0
[FF cleanup] Subscription update: use_orders_api_subscription_update_workflow

### Problem

The scope of this issue is to perform cleanup tasks for FF `use_orders_api_subscription_update_workflow` ([original rollout issue](https://gitlab.com/gitlab-org/customers-gitlab-com/-/issues/4775)).

### Proposal

Perform `Release the feature` tasks:

* [x] Create a merge request to remove `<feature-flag-name>` feature flag
  * [x] Remove all references to the feature flag from the codebase
* [x] Ensure that the cleanup MR has been deployed to both staging and production
* [x] Disable the feature flag via the [CustomersDot dashboard](https://gitlab.com/gitlab-org/customers-gitlab-com/-/feature_flags)
* [x] Ensure production environment is still working as expected (verified [logs](https://console.cloud.google.com/logs/query;query=resource.type%3D%22gce_instance%22%0A%22Zuora::Orders::OrderManagerService%22;timeRange=2023-03-08T15:43:43.199Z%2F2023-03-09T19:33:43.199Z;cursorTimestamp=2023-03-09T19:29:09.244Z?project=gitlab-subscriptions-prod) for subscription update)
* [x] Remove the Unleash feature flag from the [CustomersDot dashboard](https://gitlab.com/gitlab-org/customers-gitlab-com/-/feature_flags)
* [x] Close this issue.

Story points: 1.0
[FF cleanup] Subscription upgrade: use_orders_api_upgrade_workflow

### Problem

The scope of this issue is to perform cleanup tasks for FF `use_orders_api_upgrade_workflow` ([original rollout issue](https://gitlab.com/gitlab-org/customers-gitlab-com/-/issues/5050)).

### Proposal

Perform [`Release the feature`](https://gitlab.com/gitlab-org/customers-gitlab-com/-/issues/5050#release-the-feature) tasks:

* [x] Create a merge request to remove `<feature-flag-name>` feature flag
  * [x] Remove all references to the feature flag from the codebase
* [x] Ensure that the cleanup MR has been deployed to both staging and production
* [x] Disable the feature flag via the [CustomersDot dashboard](https://gitlab.com/gitlab-org/customers-gitlab-com/-/feature_flags)
* [x] Ensure production environment is still working as expected
* [x] Remove the Unleash feature flag from the [CustomersDot dashboard](https://gitlab.com/gitlab-org/customers-gitlab-com/-/feature_flags)
* [x] Close this issue.

Story points: 1.0
[FF cleanup] New subscription preview: use_orders_api_preview_subscription

<!-- Please complete the template below as best as you can. Make sure to check if this issue has already been raised by someone else first to avoid duplication. 

For each section below, please add screenshots or links or anything that may help visual learners understand the problem better, even if this takes you an extra minute or two this is a great help to some folks.

https://www.learning-styles-online.com/style/visual-spatial/

-->

### Problem

The scope of this issue is to perform cleanup tasks for FF `use_orders_api_preview_subscription` ([original rollout issue](https://gitlab.com/gitlab-org/customers-gitlab-com/-/issues/4648)).

### Proposal

<!-- Consult with `@gitlab-com/business-technology/enterprise-apps/zuora-architects` on the ~"Enterprise Applications" team if Zuora business logic is involved. -->

Perform [`Release the feature`](https://gitlab.com/gitlab-org/customers-gitlab-com/-/issues/4648#release-the-feature) tasks:

* [x] Create a merge request to remove `<feature-flag-name>` feature flag
  * [x] Remove all references to the feature flag from the codebase
* [x] Ensure that the cleanup MR has been deployed to both staging and production
* [x] Disable the feature flag via the [CustomersDot dashboard](https://gitlab.com/gitlab-org/customers-gitlab-com/-/feature_flags)
* [x] Ensure production environment is still working as expected
* [x] Remove the Unleash feature flag from the [CustomersDot dashboard](https://gitlab.com/gitlab-org/customers-gitlab-com/-/feature_flags)
* [x] Close this issue.

### Result

### Next steps (if any)

### How will we measure success?

Story points: 2.0
Improve the spec file spec/workers/workato/create_lead_worker_spec.rb


There are two improvments suggested during the MR review:
1. https://gitlab.com/gitlab-org/customers-gitlab-com/-/merge_requests/5984#note_1209853648
> question: Do we actually care about the return value for this worker?  I think this is fine to test, but if we don't care what it returns, then maybe it's enough to assert that it executes the service.

2. https://gitlab.com/gitlab-org/customers-gitlab-com/-/merge_requests/5984#note_1209861342
> If it is necessary, do we have a test covering this demonstrating why we need to do this?

Proposal:
  Improve the spec file spec/workers/workato/create_lead_worker_spec.rb to address the above suggestions.

Story points: 1.0
Upgrading from Starter to Premium for above 25 seats does not display error message

<!---
Please read this!

Before opening a new issue, make sure to search for keywords in the issues
filtered by the "bug" label in relevant trackers:

- https://gitlab.com/gitlab-org/gitlab/issues?label_name%5B%5D=bug
- https://gitlab.com/gitlab-org/customers-gitlab-com/issues?label_name%5B%5D=bug

and verify the issue you're about to submit isn't a duplicate.

Do not include confidential information!
--->

# Bug

When upgrading Starter to Premium as part of Renewal, and the number of seats is greater than 25, the subscription card is no longer in view and the message `Could not get the data properly. If the problem persists, contact support.` is displayed:

https://www.loom.com/share/ff16c192dd4343a5a51d3cf7c52fe5d6

[Logs](https://console.cloud.google.com/logs/query;cursorTimestamp=2022-12-15T00:32:47.977Z;query=%22A-S00174606%22%0Atimestamp%3D%222022-12-15T00:32:47.977Z%22%0AinsertId%3D%221gqh0gdf2gqgbx%22;timeRange=PT15M?project=gitlab-subscriptions-staging) indicate exceeded 25 seats maximim:

![Screen_Shot_2022-12-14_at_6.43.39_PM](/uploads/49ff0d3d1db6c1ac3d6ce3fed917b5ac/Screen_Shot_2022-12-14_at_6.43.39_PM.png)

When I tried locally, I got the following error message. I could have a few FF disabled, so I'm not sure if this is the expected behavior.

![Screen_Shot_2022-12-14_at_6.40.09_PM](/uploads/5a575efcebc1f765f611dad96788e2f4/Screen_Shot_2022-12-14_at_6.40.09_PM.png)

25 is the max. seat limit, not sure if the expected behavior shows a better error message with the subscription card. Since the FF `use_orders_api_to_preview_amendment ` is globally enabled, I did not disable on staging and test it out the behavior on staging.

## Summary

(Summarize the bug encountered concisely)

Compare with Amend API workflow, and ensure both behave the same in EoA upgrade subscription preview.

## Steps to reproduce

1. Purchase Starter self managed subscription with end date in the last 3 days ([example request](https://gitlab.com/gitlab-org/customers-gitlab-com/-/snippets/2469063) to create subscription via API)   
3. Access the subscription card in CDot   
4. Select 'Renew', select 'Premium' plan and set quantity to `26`. Observe the error

## What is the current *bug* behavior?

(What actually happens)

## What is the expected *correct* behavior?

(What you should see instead)

## Relevant logs and/or screenshots

(Paste any relevant logs - please use code blocks (```) to format console output,
logs, and code as it's tough to read otherwise.)

## Workarounds

(Ways to get around the issue)

## Reported examples

1.
1.
1.

<!---
Please add both severity and priority level according to: https://docs.gitlab.com/ee/development/contributing/issue_workflow.html#severity-labels
--->

Story points: 2.0
Subscriptions with multiple rate plans should not auto-renew (temporary)

### Problem

Subscriptions that have multiple rate plans (for the same renewable plan) are auto-renewing incorrectly. See [this comment](https://gitlab.com/gitlab-com/Finance-Division/finance/-/issues/5399#note_1209871296) for additional context. 

### Proposal

Do not auto-renew subscriptions with multiple rate plans. We are [already doing it for EOA subscriptions](https://gitlab.com/gitlab-org/customers-gitlab-com/-/merge_requests/5226), but this should be extended to all subscription.

### Result

Subscriptions with multiple rate plans do not auto-renew.

### Next steps (if any)

Fix the auto-renewal functionality to account for multiple rate plans.

### How will we measure success?

Story points: 2.0
Fix blank (not nil) zuora_account_id for customers

### Summary

There are `Customer` records in production where the `zuora_account_id` is blank (not nil)

```
Loading production environment (Rails 6.1.7)
irb(main):001:0> Customer.where(zuora_account_id: '').count
=> 132
```

We want to evaluate if this is worth fixing given we are planning to get rid of the column soon.

### Related discussion

The following discussion from !5998 should be addressed:

- [ ] @vshumilo started a [discussion](https://gitlab.com/gitlab-org/customers-gitlab-com/-/merge_requests/5998#note_1199010692):  (+2 comments)

    > **question:** Is this a double check for if there is a last minute change for the record and the `zuora_account_id` is cleared?

Story points: 2.0
Document license key and activation code generation

<!-- Please complete the template below as best as you can. Make sure to check if this issue has already been raised by someone else first to avoid duplication. 

For each section below, please add screenshots or links or anything that may help visual learners understand the problem better, even if this takes you an extra minute or two this is a great help to some folks.

https://www.learning-styles-online.com/style/visual-spatial/

-->

### Problem

It is currently not documented how these processes work. We should add documentation for GitLab stakeholders to figure this out.

### Proposal

<!-- Consult with `@gitlab-com/business-technology/enterprise-apps/zuora-architects` on the ~"Enterprise Applications" team if Zuora business logic is involved. -->

Add this to the docs in this repository:

1. [This is the code](https://gitlab.com/gitlab-org/customers-gitlab-com/-/blob/9ae796fa8060281378ff6800f2ad0aefa582821b/app/models/license.rb#L218) that creates a `GitLab::License` (that’s the object from the `gitlab-license` gem). We use this object within our `License` model. The referenced code is called on [creation](https://gitlab.com/gitlab-org/customers-gitlab-com/-/blob/9ae796fa8060281378ff6800f2ad0aefa582821b/app/models/license.rb#L84) of a `License` object only.
1. [This is the code](https://gitlab.com/gitlab-org/customers-gitlab-com/-/blob/1219d82057ecc80468e9c515587ee24a185b9111/app/models/subscription.rb#L441-457) that creates the activation code which is stored in our `CloudActivation` model. This code is called during a Zuora callback [here](https://gitlab.com/gitlab-org/customers-gitlab-com/-/blob/4e3b474803252e89bc46ac679932fa836f7acf6c/app/workers/zuora_callback_worker.rb#L23) and also when the [controller action](https://gitlab.com/gitlab-org/customers-gitlab-com/-/blob/74259337a9748b56e2412d98d016704810b63d4b/app/controllers/subscriptions_controller.rb#L104) `subscriptions#create` is used (which comes down to this code).

Story points: 1.0
Hide tooltip and term duration for CI minutes purchase

### Problem

On customers staging, when purchasing CI minutes, the date of purchase is displayed as 1 day. 

The tooltip information next to it displays, `Your storage subscription has the same term as your main subscription, and the price is prorated accordingly.`

Additional CI minute purchases are added onto your existing subscription (if available), the duration of the term is for the existing subscription. But CI minutes are valid for 1 year after the purchase date, so the start date of the subscription is irrelevant and confusing making the term duration incorrect.

![image](/uploads/90d1625971575eb01a41dc43c62dfceb/image.png)


_PS - The error might also be occurring on the Production server._ 

### Proposal

Tooltip and the term duration shouldn't be displayed for CI minutes purchase flow. They apply only for Storage purchase. (similar to how we handle this on GitLab.com)


### Result

### Next steps (if any)

### How will we measure success?

Story points: 1.0