Add quantity summary to billing purchase history when available

[olaseni]

Changes proposed in this Pull Request

• Retrieves new parameters licensed_quantity_summary and new_quantity for purchase history line items and details and uses it to display contextual information for products with upgradeable quantities.

This PR depends on changes from code-D56964.

The purchase billing history UI should look similar to this after changes.

Testing instructions

• Ensure code-D56964
• Checkout this branch
• Visit your billing history page i.e. /purchases/subscriptions/. You may still need to click on Billing history
• Confirm that the products with upgradeable quantities i.e. Email display meaningful description i.e. quantity upgrades.

[matticbot]

Test live: https://calypso.live/?branch=update/add-quantity-summary-to-billing-history

[matticbot]

Here is how your PR affects size of JS and CSS bundles shipped to the user's browser:

Sections (~379 bytes added 📈 [gzipped])

name            parsed_size           gzip_size
site-purchases      +2014 B  (+0.2%)     +379 B  (+0.1%)
purchases           +2014 B  (+0.1%)     +379 B  (+0.1%)

Sections contain code specific for a given set of routes. Is downloaded and parsed only when a particular route is navigated to.

Legend

What is parsed and gzip size?

Parsed Size: Uncompressed size of the JS and CSS files. This much code needs to be parsed and stored in memory.
Gzip Size: Compressed size of the JS and CSS files. This much data needs to be downloaded over network.

Generated by performance advisor bot at iscalypsofastyet.com.

[sirbrillig]

This seems fine to me although I do have a concern about how the "(renewal)" text added by the backend is localized. Discussion on the backend patch.

[stephanethomas]

I agree with the concerns raised by Payton in the server patch.

1 new mailbox. Total malboxes: 13 (upgrade)

I really think we should avoid this upgrade term in user-facing content when we want to refer to the process of adding new mailboxes. It's not clear enough, and we use it for other things such as subscriptions (e.g. see the Active Upgrades tab) . I'm also not sure why we need to display the total number of mailboxes, so I would suggest just the following:

Purchase for 1 new mailbox

In order to be consistent, we could have the following for renewals:

Renewal for 13 mailboxes

Also, let's ping @Wesco for feedback ☺.

[olaseni]

I understand where you are coming from @stephanethomas . I was initially trying to be consistent with some of the billing emails we already send on purchase, but I think your points are valid.

Of course, I would not mind to get @wensco opinion into the mix.

[hambai]

Tested this and it looks okay. I left a small comment on the copy.

[stephanethomas]

We should probably use %(quantity)d instead of %(quantity)s.

[a8ci18n]

This Pull Request is now available for translation here: https://translate.wordpress.com/deliverables/5534928

Thank you @olaseni for including a screenshot in the description! This is really helpful for our translators.

[a8ci18n]

Translation for this Pull Request has now been finished.