cc: Fix multiple outstanding output surface requests

cc: Fix multiple outstanding output surface requests

SingleThreadProxy was previously not considering
DidFailToInitializeOutputSurface responses as an outstanding
RequestNewOutputSurface call. This would cause the embedder to start
servicing an output surface request, then composite, receive another,
and then have double output surface requests.

The fix is to consider this failure state as a request.

TBR=danakj@chromium.org,jbauman@chromium.org,sievers@chromium.org
BUG=444277
Review URL: https://codereview.chromium.org/871743002

Cr-Commit-Position: refs/heads/master@{#313357}
(cherry picked from commit 5232fbbf8df7e06471950a12bc041c766e31a997)

Committed: https://chromium.googlesource.com/chromium/src/+/647161e2a8fa4dfdaac0c1f1b263e70bf8d483f6

[enne (OOO), 2015-02-05 19:03:12]

Committed patchset #1 (id:1) manually as
647161e2a8fa4dfdaac0c1f1b263e70bf8d483f6 (presubmit successful).