[Feature] [WIP] Require progress to be output on Magento Cli command methods that will take more than a minute to execute

Nobody has claimed this yet.

### Description (*)
As a developer, I'd like to see progress output for any step of a Magento Cli command that can potentially run longer than one minute.

### Expected behavior (*)
A standard should be in place requiring any command to output progress for a method that will take longer than one minute to execute.

For example: `bin/magento setup:upgrade` @ `Installing data...` should update progress after each module data install that has completed. In the circumstance that sample data is being deployed, this can take a very long time to complete.

### Benefits
Knowing that the command is not stuck

### Additional information
Nothing else to add.

Start with the bin/magento setup:upgrade example and the “Installing data...” step described in the issue. Trace which command methods can exceed one minute and identify the relevant command entry points. Done means a project-wide standard is defined and long-running steps report progress, including each completed module data install.

Written by the indexing model from the issue text.