EPIC: create-plugin update command improvements

[tolzhabayev]

Goals

We would like to improve the create-plugin update command so it can do more sophisticated updates to the plugins. We are planning to call these tailored and more sophisticated updates "migrations".

Migrations could:

• update github workflows
• update specific NPM dependencies, or groups of NPM dependencies
• update and/or add files in the project (not just the ones inside the .config folder)
• update package.json scripts

Another key goal is to make it possible to reliably test changes to the update command, something that we are lacking now. As from now on mutating operations can only happen through migration scripts, we will achieve this goal by testing the migration scripts.

Tasks

Preview Give feedback

1. Define the metadata for the migrations (id, description, information on which versions to run it for)
2. Create a migration manager to orchestrate the entire update process when the command is run.
3. Create a context for the migration manager to perform file system operations. It should provide a way to make it easy
4. Adjust log messages so they display the necessary information in an easy-to-read format
5. Create a way to test migration scripts
6. Add an automated test that checks if the migration scripts are idempotent
7. Create a way to share helpers with the migration scripts: the goal is to make it possible for devs writing migrations to perform the most common tasks: updating dependencies, formatting code, running package manager commands, build config files from the handlebars templates.
8. Add an eslint rule that forbids migrations from importing node:fs to make sure they always use migration manager context

Ongoing work

The ongoing work is currently available on the updates-as-migrations-pt1 branch.

If we want we can incrementally roll these things out without changing the current update command behaviour and use an arg of some sort to fine tune before flipping the switch.

Fixes: #820
Related:

• Create Plugin: Make migrate / update smarter #261
• add CI workflows to migrate? #61