Add to WindowsExitCode enum

Add defined content and chrome exit codes, as well as commonly seen Windows errors to the WindowsExitCode enum

BUG=412384
Committed: https://crrev.com/f3feaa9c705b4a844ec37d52cb91c12e8c9e8dd9
Cr-Commit-Position: refs/heads/master@{#305870}

[Sigurður Ásgeirsson, 2014-11-26 16:55:54]

siggi@chromium.org changed reviewers:
+ mpearson@chromium.org

[Sigurður Ásgeirsson, 2014-11-26 16:55:55]

PTAL

[Sigurður Ásgeirsson, 2014-11-26 16:57:48]

Ooops, hold off a little - I goofed in the content codes..

[Sigurður Ásgeirsson, 2014-11-26 17:05:22]

On 2014/11/26 16:57:48, Sigurður Ásgeirsson wrote:
> Ooops, hold off a little - I goofed in the content codes..

Ok, fixed now. Please take a look.

[Mark P, 2014-11-26 19:10:12]

rubber stamp lgtm
(I assume those code are right.)

--mark

[Sigurður Ásgeirsson, 2014-11-26 19:10:37]

The CQ bit was checked by siggi@chromium.org

[commit-bot: I haz the power, 2014-11-26 19:11:14]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/759313002/20001

[commit-bot: I haz the power, 2014-11-26 20:31:28]

Committed patchset #2 (id:20001)

[commit-bot: I haz the power, 2014-11-26 20:32:15]

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

[gab, 2014-12-02 21:56:33]

gab@chromium.org changed reviewers:
+ gab@chromium.org

[gab, 2014-12-02 21:56:33]

Just had a thought, see inline below to avoid being bitten by a benign change in
the future.

https://codereview.chromium.org/759313002/diff/20001/tools/metrics/histograms...
File tools/metrics/histograms/histograms.xml (right):

https://codereview.chromium.org/759313002/diff/20001/tools/metrics/histograms...
tools/metrics/histograms/histograms.xml:56749: +  <int value="4"
label="chrome::RESULT_CODE_INVALID_CMDLINE_URL"/>
Be aware though that all codes below are subject to be bumped if
content::RESULT_CODE_LAST_CODE goes up (because of [1]).

I suggest adding a comment @ [2] to update this enum should it indeed be bumped
to avoid a headache looking for the wrong culprit if it does.

[1]
https://code.google.com/p/chromium/codesearch#chromium/src/chrome/common/chro...

[2]
https://code.google.com/p/chromium/codesearch#chromium/src/content/public/com...

Also note that UMA doesn't have a nice way to provide histogram definitions per
milestone... so if someone correctly adjusts this on trunk, the dashboards will
be all messed up for values coming from Stable/Beta which would still be
reporting the "old" exit codes...