Tempest Shares client should catch error_delete status for other resources

[Andrew Kerr]

The shares client in tempest currently catches if a share is in 'error_deleting'
state and throws a ResourceReleaseFailed exception so the tests don't have
to wait for the timeout.

However, more resources than just shares can go into error_deleting state,
snapshots for example

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/206116

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/206116
Committed: https://git.openstack.org/cgit/openstack/manila/commit/?id=22bd34a04c09b46c834052281f9328f85af2015b
Submitter: Jenkins
Branch: master

commit 22bd34a04c09b46c834052281f9328f85af2015b
Author: Andrew Kerr <email address hidden>
Date: Wed Jul 8 09:36:25 2015 -0400

    Catch error_deleting state for more resources than just shares

    The shares client in tempest currently catches if a share is in 'error_deleting'
    state and throws a ResourceReleaseFailed exception so the tests don't have
    to wait for the timeout.

    However, more resources than just shares can go into error_deleting state,
    snapshots for example. This patch changes the check for error_deleting to
    work with all resource types.

    closes-bug: 1477703

    Change-Id: Idc530db6593769df8f503878ce7432270ddae086