[api] marks environments deleted regardless of actual state

[Steve McLellan]

When an environment is deleted it's immediately removed from the database; instead it should follow the same pattern as creation:
* Create a session in state 'deleting'
* Mark deployment state as 'deleting'
* Send RPC call
* On success, finally remove the environment

Primary reason for this is because it's much neater for the user, and in cases where users are being charged for resources, it could be extremely misleading to assume everything's been cleared up properly.

[OpenStack Infra (hudson-openstack)]

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

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/109508
Committed: https://git.openstack.org/cgit/stackforge/murano/commit/?id=56b2d5df276699c33b08298b6a592b8a1ebafe20
Submitter: Jenkins
Branch: master

commit 56b2d5df276699c33b08298b6a592b8a1ebafe20
Author: Stan Lagun <email address hidden>
Date: Fri Jul 25 11:06:56 2014 +0400

    Fixes silent deletion of environments

    Now environment deletion is done as a regular deployment that can fail.
    Environments that are deleted, but deletion process has failed remain in database
    and shown in dashboard with status 'delete failure'. Environments that are being deleted
    has status 'deleting' and do not disappear before they really got deleted on engine side

    Also improved status reporting for environments. Now it also reports status of last deployment -
    'deploy failure', 'delete failure'

    P.S. Functional tests were slightly refactored and fixed to reflect changes
    in deletion logic

    Change-Id: I05625dd71f7ca9559bb88319b26b122214f15019
    Closes-Bug: #1325101