Description of problem:

When running `foreman-maintain backup -y --wait-for-tasks`, if there are running tasks that don't finish in the default timeout, the backup will fail.

. . .
There are 4 running tasks.                                                                                
| Waiting 10 seconds before retry.
Timeout: execution expired. Try again.          [OK]
--------------------------------------------------------------------------------
Rerunning the check after fix procedure
Check for running tasks:                        [FAIL]
There are 4 active task(s) in the system.
Please wait for these to complete or cancel them from the Monitor tab.
--------------------------------------------------------------------------------
Check still failing after attempt to fix. Skipping
Scenario [Backup] failed.

It would be desirable to show some information regarding those tasks to be able to analyze them.

How reproducible:

Always that the tasks that don't finish within the default timeout

Is this issue a regression from an earlier version:

No.

Steps to Reproduce:

1. Run a Foreman backup with `-y --wait-for-tasks` when there are running (long term?) tasks running that won't end up before the default timeout.

2.

3.

Actual behavior:
[Describe the issue in detail, including what is happening and where]

Expected behavior:
It would be nice if at least the tasks ID was printed.

Business Impact / Additional info: