[TECH DEBT] Start using migration "tags" instead of relying on migration groups

[rosiel]

Overview of feature request

Paraphrase from @adam-vessey:

Drush is starting to [which versions?] include on its own the functionality that we currently get from the migrate_plus [wrong; see Adam's comment below] module.

Islandora Core Feature, Islandora Defaults, and potentially others ship migrations that use the "migrate_group" parameter provided by migrate_plus [oops, migrate_tools rather]. (They also live in a config structure called migrate_plus.migration.[migration_name].yml and we might want to address that too?) However new Drush does not come with this option. It does however have a "tag" parameter we can use

We should give our existing migrations "tags" so that we can maybe run them without migrate_plus.

[adam-vessey]

Looks like Drush rolled its own migrate:import, :rollback, etc as of 10.4.0 (the commit introducing it: drush-ops/drush@302bda8).

Also, just for reference, the present migrate:import is from the migrate_tools module... migrate_tools' implementation does support migrate_plus' concept of a migration_group; however, it's not a concept shared by the base migrate module plugins structure; however yeah, migration_tags can be an array of values to the same end.

From the migrate_tools project page:

Since Drush 10.4 many of the drush commands are also available in Drush core. The code-base that made its way into Drush 10.4 was from an earlier and simpler fork of this module's code. For example, Drush does not support migrate plus config entities or provide a progress bar. Over time, the Drush team continues to add features and some of this might become incorporated upstream. The support team for Drush is unique from migrate tools. Any features or support requests for Drush core should be handled in its Github issue queue.

[github-actions]

This feature request issue is being marked as stale from inactivity and will be automatically closed in 2 weeks unless further action is taken. If this issue is still relevant please comment. Please also consider attending the weekly Tech Call to discuss the issue