SignalResponder, set resource_id in the correct place

If there is an error creating the ec2 keypair, but we have created
a user, we will lose track of the user id and be unable to delete

Change-Id: Ib8704f1054dd16003849700c659d0fea83c13916
Closes-Bug: #1262177
wsgi.Resource exception handling to not log errors

In order to not log some exceptions as errors, the
wsgi.Resource.__call__() was modified.
Instead of check if an exception is a HTTPBadRequest or a HTTPNotFound,
now all the exceptions that are not childs of HTTPError are raised
directly, without logging, translation or disguise.
If the exception is a child of HeatException, then the exception is
tranlated but not logged as an error. When this exception reaches the
Fault Wrapper Middleware it is logged as debug.
Some unused, or only use in test, exceptions were removed.

Change-Id: I105eeb74a55dcabc79cd3926dd88da0e19d1e1f1
Closes-Bug: #1231133
Merge "wsgi.Resource exception handling to not log errors"
Merge "SignalResponder, set resource_id in the correct place"