Don't extend MigrateToolsCommands

Problem/Motivation

In \Drupal\path_redirect_import\Drush\Commands\PathRedirectImportCommands, we're extending an internal class of another contrib module, and that means an existing install of path redirect import can be broken by upgrading the other contrib project. It also means code churn chasing any changes in the contrib module.

Steps to reproduce

Proposed resolution

Rather than extending \Drupal\migrate_tools\Drush\Commands\MigrateToolsCommands, it might be worth either:

• directly using the migrate tools services (not the drush command); or
• invoking the drush command programmatically, rather than via a class method.

I think this would make it less likely the module will suddenly break on people and require less maintenance.

Remaining tasks

User interface changes

API changes

Data model changes