Teardown benchmark resources in reverse order

Say our benchmark looks as follows:

sut:
  resources:
  - configMap:
      name: "sut-configmap-1"
      files:
      - "sut-file-1.yaml"
      - "sut-file-2.yaml"
  - configMap:
      name: "sut-configmap-2"
      files:
      - "sut-file-3.yaml"
loadGenerator:
  resources:
  - configMap:
      name: "load-generator-configmap"
      files:
      - "load-generator-file-1.yaml"
      - "load-generator-file-2.yaml"

The Kubernetes resources should be deployed in the following order:

1. sut-file-1.yaml
2. sut-file-2.yaml
3. sut-file-3.yaml
4. load-generator-file-1.yaml
5. load-generator-file-2.yaml

After an SLO experiment, the resources should removed in the following order:

1. load-generator-file-2.yaml
2. load-generator-file-1.yaml
3. sut-file-3.yaml
4. sut-file-2.yaml
5. sut-file-1.yaml

The order should also be persevered (or rather reversed) when not having the files property set.

Extensive testing is required.