Pricing Page: Fix duplicate Backup product card showing when Jetpack Starter Plan is owned.

[elliottprogrammer]

Now that the Jetpack Starter plan has been added as a new purchasable product on the pricing page, There was a bug that was causing duplicate VaultPress Backup product cards to show on the pricing page (when logged-in and the site is in context) when the Jetpack Starter plan is owned. See Screenshot:

.

.

---

.
This PR fixes this bug whereas when a site has a subscription for the Jetpack Starter plan, The VaultPress Backup product card will only show once, and it will be labeled "Part of the current plan" with a "Manage subscription" CTA button, instead of showing 2 VaultPress Backup product cards.
(See After screenshot:)

Asana Task: 1198218726984184-as-1204541714823225/f

Proposed Changes

• Allowed JETPACK_BACKUP_T0 to be recognized as an "owned" product on the pricing page.

Testing Instructions

• Spin up this PR: git fetch && git checkout add/backupT0-product-to-owned-products-pricing-page && yarn start-jetpack-cloud
• If you don't already have a site that owns a subscription to the new Jetpack Starter plan, the you'll need to Purchase Jetpack Starter create an ephemeral or Jurassic Ninja site, connect Jetpack, and activate the product on the site.
• Next go to http://jetpack.cloud.localhost:3000/pricing/:SITE (replace :SITE with the site-slug of the site you have your Jetpack Starter plan on.
• Make sure you are logged-in. If not, log in and reload the /pricing/:SITE page.
• Verify that the VaultPress Backup product card is not duplicated and it is showing as "Part of the current plan" (like the "After" screenshot shown above)..

Pre-merge Checklist

• Has the general commit checklist been followed? (PCYsg-hS-p2)
• Have you written new tests for your changes?
• Have you tested the feature in Simple (P9HQHe-k8-p2), Atomic (P9HQHe-jW-p2), and self-hosted Jetpack sites (PCYsg-g6b-p2)?
• Have you checked for TypeScript, React or other console errors?
• Have you used memoizing on expensive computations? More info in Memoizing with create-selector and Using memoizing selectors and Our Approach to Data
• Have we added the "[Status] String Freeze" label as soon as any new strings were ready for translation (p4TIVU-5Jq-p2)?
• For changes affecting Jetpack: Have we added the "[Status] Needs Privacy Updates" label if this pull request changes what data or activity we track or use (p4TIVU-ajp-p2)?

[github-actions]

Calypso Live (direct link)

https://calypso.live?image=registry.a8c.com/calypso/app:commit-3091ffbe8b679538ec31c9ae0d0a616e9b6f47b4

Jetpack Cloud live (direct link)

https://calypso.live?image=registry.a8c.com/calypso/app:commit-3091ffbe8b679538ec31c9ae0d0a616e9b6f47b4&env=jetpack

[matticbot]

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

Sections (~12 bytes added 📈 [gzipped])

name                   parsed_size           gzip_size
plans                        +40 B  (+0.0%)      +12 B  (+0.0%)
jetpack-connect              +40 B  (+0.0%)      +12 B  (+0.0%)
jetpack-cloud-pricing        +40 B  (+0.0%)      +12 B  (+0.0%)

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.

[CodeyGuyDylan]

Tested well, looks simple enough to me, no issues I see 😄