Retry Set RequestContextObject for PNaCl pexe fetches, to fix On-Demand update.

Retry Set RequestContextObject for PNaCl pexe fetches, to fix On-Demand update.

There was a race condition in the added test check in the previous
attempt. That made the test Super Flaky. This is more noticeable in the
Release builds than the Debug build that I was working with.
(see https://codereview.chromium.org/471233003/)

With a Release build I was able to repro the flakiness (40% failure
over 200 runs). After the fix, I tested 500 runs and the success rate
is now 100%. I can't say it won't flake for other reasons, but
this fixes the main flake that was introduced. Historically,
the test does ocassionally need to be retried due to timeouts,
according to the bot log history. We may want to split the
CORS and the non-CORS test case to see if that will help w/ timeouts.

I didn't want to do that for this patch, since it would get
much more complicated and this is intended for merging to M38.

Retry with the race condition fixed. Also re-enable the test since
it got disabled by another CL for being flaky.

BUG=401755
BUG=315328
Committed: https://crrev.com/efd4b3c8968ae61cdfcdbce0f8068e98b5cea6ff
Cr-Commit-Position: refs/heads/master@{#292807}

[jvoung (off chromium), 2014-08-29 17:49:10]

jvoung@chromium.org changed reviewers:
+ ncbray@chromium.org, teravest@chromium.org

[Nick Bray (chromium), 2014-08-29 22:43:35]

owners LGTM

[jvoung (off chromium), 2014-08-30 21:24:10]

The CQ bit was checked by jvoung@chromium.org

[commit-bot: I haz the power, 2014-08-30 21:25:00]

CQ is trying da patch. Follow status at
 https://chromium-status.appspot.com/cq/jvoung@chromium.org/524683002/20001

[commit-bot: I haz the power, 2014-08-30 21:49:47]

Committed patchset #2 (id:20001) as 7f61515a1fc5c236a9b7ae32305fd282810d8605

[commit-bot: I haz the power, 2014-09-10 03:14:49]

Patchset 2 (id:??) landed as
https://crrev.com/efd4b3c8968ae61cdfcdbce0f8068e98b5cea6ff
Cr-Commit-Position: refs/heads/master@{#292807}