Description of problem:
Having a job execution that user cancels in the middle, then:

• job execution details does show proper number of successfull/failed/.. and cancelled counts, but
• task details of the RunHostsJob task does count the tasks that were running but cancelled as failed

That is incoherent and quite confusing esp. when support engineers get (html) task export and try to deduce the job output stats.

Version-Release number of selected component (if applicable):
any (6.11 till 6.15 snap 3)

How reproducible:
100%

Steps to Reproduce:
1. hammer job-invocation create --search-query "id ^ (3)" --job-template "Run Command - Script Default" --inputs "command='sleep 60'" --async
2. hammer job-invocation cancel --id 10 # the ID from previous output
3. Optionally, run a job with concurrency 2 against 4 Hosts and cancel it during the first "batch".
4. Check dynflow console of the RunHostsJob task (in WebUI or in html task export) and compare it with job invocation statistics

Actual results:

• Task from 1. has task with "failed_count: 1" but "cancelled_count: 0".
• Task from 3. has "failed_count: 2" and "cancelled_count: 2".

Expected results:

• Task from 1. should have "failed_count: 0" and "cancelled_count: 1".
• Task from 3. should have "failed_count: 0" and "cancelled_count: 4".

Additional info: