Redundant resource deletion for heat resource cleanup

[Kairat Kushaev]

During writing one of tests I found the following definition of Heat cleanup manager in rally.context.cleanup.resources:
@base.resource("heat", "stacks", order=100)
class HeatStack(base.ResourceManager):
    pass
The definition above means that rally is trying to cleanup resources (=stacks for Heat) for every user because tenant_resource option is not defined and the default value for this attribute is False.
But it turns out that heat stacks are tenant based and tenant stacks are available for all users in project. So there is no need to delete stacks for every user.
Heat supports deletion in cycle (=deletion of the same resource several times) but it definitely leads to some overhead because when the new deletion begins the previous deletion jobs has stopped.

So I propose to define the new behavior for heat cleanup manager in order to get rid of this overhead during testing.