Harness should specify tear-down steps explicitly

Currently, the de facto convention for cleaning up harness-runner resources is to execute a non-rendered cleanup step. This is often configured as part of the `prod` steps, which are the final set executed by the runner.

A cleaner option may be to have an explicit tear-down specification (with steps) at the top level in the yml.

As reported by @rspurgeon