feat(upgrade): run migrations from upgrade cli

[tay1orjones]

Closes #10466

This PR updates the @carbon/upgrade CLI to be able to run one or more migrations as part of an upgrade flow. These migrations contain a migrate function that can run jscodeshift codemods.

The following is now possible:

• @carbon/upgrade: upgrade and run all available migrations for a given upgrade
• @carbon/upgrade migrate: prompt a list of all available migrations, select one to run removed based on feedback
• @carbon/upgrade migrate list: list all available migrations
• @carbon/upgrade migrate <migration-name>: run a specific migration

Changelog

New

• Provide new migrate command to run and list individual migrations
• Add a new imports-to-unified-package.js codemod to rewrite imports from carbon-components-react to @carbon/react moved to feat(upgrade): add codemod, rewrite imports to @carbon/react #10523

Changed

• Modify the upgrade flow to run all available migrations for a given upgrade flow by default
• Move transforms from codemods package to live within the upgrade package

Removed

• Remove codemods package

Testing / Reviewing

• Try out the CLI locally by:
  • Pulling down this PR
  • Run cd packages/upgrade
  • Run yarn build to build the CLI
  • Run cd fixtures/sample-project to use our sample project fixture
  • Run ../../bin/carbon-upgrade.js --help to verify the CLI is up-and-running
  • Take a look at the options / capabilities of what's there to see if it makes sense
  • Run ../../bin/carbon-upgrade.js and choose an upgrade path. Verify the CLI runs all the available migrations for that upgrade path. In the case of v11: carbon-components, two stub migrations should be called and log out to the console.
  • Run ../../bin/carbon-upgrade.js migrate list to see a list of migrations should be shown
  • Run ../../bin/carbon-upgrade.js migrate to see a prompt of migrations should be shown allowing a single selection removed based on feedback

[netlify]

✔️ Deploy Preview for carbon-react-next ready!

🔨 Explore the source changes: 904f70e

🔍 Inspect the deploy log: https://app.netlify.com/sites/carbon-react-next/deploys/61f2d32ac680430007b04e6a

😎 Browse the preview: https://deploy-preview-10494--carbon-react-next.netlify.app

[netlify]

✔️ Deploy Preview for carbon-elements ready!

🔨 Explore the source changes: 904f70e

🔍 Inspect the deploy log: https://app.netlify.com/sites/carbon-elements/deploys/61f2d32adca11a00073e430a

😎 Browse the preview: https://deploy-preview-10494--carbon-elements.netlify.app

[netlify]

✔️ Deploy Preview for carbon-components-react ready!
Built without sensitive environment variables

🔨 Explore the source changes: 904f70e

🔍 Inspect the deploy log: https://app.netlify.com/sites/carbon-components-react/deploys/61f2d32a301159000855a521

😎 Browse the preview: https://deploy-preview-10494--carbon-components-react.netlify.app

[joshblack]

Was thinking about this the other day, one thing that could simplify our upgrade paths is that we blanket run migrations associated with the upgrade (in this case we would not prompt users to select migrations).

For those who would like to select a specific migration, we could have a migrate command that is like:

• @carbon/upgrade migrate list, list all available migrations
• @carbon/upgrade migrate <name>, run the migration with the given name

[tay1orjones]

@joshblack Great point! Having to navigate through the upgrade flow to run a migration is cumbersome.

I just pushed an update to run all migrations with an upgrade, and provide separate migrate commands to run migrations individually.

[tay1orjones]

@joshblack Amazing suggestions, thank you! All have been addressed and feedback incorporated. execa works great, and getting the bin directly like you proposed was flawless ✨

[tay1orjones]

I've removed the imports-to-unified-package codemod and put it in it's own PR based off of this PR, #10523

The cli now runs the icons-react-size-prop codemod instead

[joshblack]

🎉 🚀