Include error status code in console message for non-CORS response.

Include error status code in console message for non-CORS response.

While CORS is concerned with the access control headers that come
back in the response and not its status code, an error response
(status code >= 400) containing no CORS headers is most likely an
indication of the server not being configured correctly.

To potentially help the user/developer more quickly diagnose that as
the problem, include the status code in the console message that's
emitted for the failed CORS resource sharing check.

R=
BUG=269192
Committed: https://src.chromium.org/viewvc/blink?view=rev&revision=177116

[sof, 2014-06-27 12:09:10]

Please take a look.

This is sometimes a source of CORS debugging confusion for users/developers; I
think we should try to help out.

[abarth-chromium, 2014-06-27 15:38:54]

lgtm

[commit-bot: I haz the power, 2014-06-27 15:39:26]

CQ is trying da patch. Follow status at
 https://chromium-status.appspot.com/cq/sigbjornf@opera.com/332633006/20001

[tyoshino (SeeGerritForStatus), 2014-06-27 16:03:56]

lgtm

[commit-bot: I haz the power, 2014-06-27 16:54:10]

Change committed as 177116