enabling trove to work in multi-region deployment

In a multi-region environment with trove in both, troveclient
currently throws an error regarding ambiguous endpoints if a
region_name kwarg is not passed in. Now passing in the
services_region.

Change-Id: I0a2cea3d532680549a594e8bf0e9df1d15f37cde
Closes-bug: #1227888
Convert generator to list in Heat list API call

The generator being returned by heatclient didn't like
being iterated multiple times (as when doing a multiple
delete through the stacks table).

Fixes bug #1224393

Change-Id: I01482c0fadcf145fe99806983d9a1dc6f50ac56a
Merge "enabling trove to work in multi-region deployment"
Merge "Convert generator to list in Heat list API call"