Plans Next: Migrate the Features list/metadata to @automattic/calypso-products

[chriskmnds]

This is part of uncoupling the plans-grid components for enabling and exploring use outside of Calypso.

We have so far worked around the FEATURES_LIST definition living locally in Calypso by passing it into the components as a prop. However, that only allowed us to migrate the grid components to a package. We need to address the features list definition of living locally now. We cannot possibly use the plans-grid package in an external environment without the list of features.

It's not a straight-up migration as FEATURES_LIST has a few local dependencies - icons, ExternalLinkWithTracking component, etc. We will piece-meal the migration. Similarly to the AddOns metadata migration (#81374), we have created an exploratory PR (#88186) with TODOs and a list of tasks below.

Tasks

Preview Give feedback

1. Migrate ExternalLink component to @automattic/components #88181
   Plans: NPM essential +1
   
2. Plans Next: Migrate assets/svgs imported in features-list to packages #88182
   Plans: NPM essential +1
   
3. Plans Next: Migrate lib/url/support.js to a new package #88183
   Plans: NPM essential +1
   
4. Plans Next: Migrate features-list to @automattic/calypso-products #88186
   Plans: NPM essential +1
   

[chriskmnds]

Handling a partial solution to uncouple plans-features-2023-grid in #79733. Specifically the following:

as a more realistic/faster alternative we can consider passing features-list as a prop and localise the getPlanFeaturesObject method in plans-features-2023-grid

cc @southp (we'll still need these ported into calypso-products, but with #79733 it will no longer be a blocker to package extraction

[southp]

Thansk for the heads up. Good to know that you've identified a way around it :)
Also cc @jdc91 here since I've recommended him to look into this issue the other day.

[chriskmnds]

Update: Updated the description and added a list of tasks to handle this migration. There's a bit to do, although it will also contribute to the overall hygiene e.g. #88183 will be cleaning up more than just serving the Plans NPM migration