Add test steps to report in order of completion

[nirs]

We start all the test together, and add them to the report in the same order of the yaml.

- duration: 975.93285225
  items:
  - duration: 665.6801172899999
    items:
    - duration: 30.060434125
      name: deploy
      status: passed
    - duration: 90.074990416
      name: protect
      status: passed
    - duration: 360.253114
      name: failover
      status: passed
    - duration: 130.095826583
      name: relocate
      status: passed
    - duration: 49.156933208
      name: unprotect
      status: passed
    - duration: 6.038818958
      name: undeploy
      status: passed
    name: appset-deploy-rbd
    status: passed
  - duration: 975.9325389599999
    items:
    - duration: 40.072125167
      name: deploy
      status: passed
    - duration: 60.0505515
      name: protect
      status: passed
    - duration: 390.27122525
      name: failover
      status: passed
    - duration: 420.295370334
      name: relocate
      status: passed
    - duration: 59.198251542
      name: unprotect
      status: passed
    - duration: 6.045015167
      name: undeploy
      status: passed
    name: appset-deploy-cephfs
    status: passed
  - duration: 536.013269834
    items:
    - duration: 20.110296334
      name: deploy
      status: passed
    - duration: 90.0836925
      name: protect
      status: passed
    - duration: 210.466586792
      name: failover
      status: passed
    - duration: 145.104456208
      name: relocate
      status: passed
    - duration: 64.198486958
      name: unprotect
      status: passed
    - duration: 6.049751042
      name: undeploy
      status: passed
    name: subscr-deploy-rbd
    status: passed
  - duration: 775.964653583
    items:
    - duration: 20.11021125
      name: deploy
      status: passed
    - duration: 90.083575125
      name: protect
      status: passed
    - duration: 270.312483916
      name: failover
      status: passed
    - duration: 330.214696
      name: relocate
      status: passed
    - duration: 59.19304825
      name: unprotect
      status: passed
    - duration: 6.050639042
      name: undeploy
      status: passed
    name: subscr-deploy-cephfs
    status: passed
  - duration: 494.299300958
    items:
    - duration: 6.194759917
      name: deploy
      status: passed
    - duration: 95.088601584
      name: protect
      status: passed
    - duration: 206.098790125
      name: failover
      status: passed
    - duration: 123.095901333
      name: relocate
      status: passed
    - duration: 56.189390583
      name: unprotect
      status: passed
    - duration: 7.631857416
      name: undeploy
      status: passed
    name: disapp-deploy-rbd
    status: passed
  - duration: 734.978609707
    items:
    - duration: 6.1947735
      name: deploy
      status: passed
    - duration: 95.089987083
      name: protect
      status: passed
    - duration: 300.194057875
      name: failover
      status: passed
    - duration: 265.553865042
      name: relocate
      status: passed
    - duration: 60.189739291
      name: unprotect
      status: passed
    - duration: 7.756186916
      name: undeploy
      status: passed
    name: disapp-deploy-cephfs
    status: passed

This makes checking test timing harder. It will be more useful to add the test to the report in the order they complete.

Instead of iterating over the tests list, add completed tests to a channel, and add tests to the report in the order we get them from the channel. Similar to the way we handle gather data/s3 results.

This also matches the way go test display parallel test results.