Inspect error.response.body, not error.message

Recent versions of excon have a middleware component,
Excon::Middleware::Expects and fog requests mostly record an expectation
of a 200 status code. Some calls to AWS return status other than 200 and
in some cases the error handling obscures the underlying error.

Current handling parsed error.message; this instance of error is
constructed by excon and includes the response as an attribute. The
message is always something like 'Expected(200) <=> Actual(404 Not Found)'
and so the parsing never succeeds.

Instead we now attempt to parse error.response.body which should allow
extraction of the underlying AWS Code value, which in turn will produce
an exception that points to the actual underlying cause.
Refactor error handling

Match against the error object in both the old (against error.message)
and the new (against error.response.body); return a hash from this
method.

In the rescue block, try hard to raise an exception that includes the
code and message extracted from the error.
Remove code from other branch-in-progress
Remove mistaken version update
Construct hash with => (for 1.8.7)
Use specific error classes, not generic Fog::Compute::AWS::Error
Merge pull request #1935 from jbence/feature/update_AWS_error_handling

[aws] Update aws error handling