Reorder GenerateStateFromBeaconAndAttemptCount.

Reorder GenerateStateFromBeaconAndAttemptCount.

I think the older order could result in incorrect behavior if Chrome
crashed during startup. This might help with the bug as well.

BUG=406475
Committed: https://crrev.com/619b85aaed93f95207dc9c06fa85fe14cb91c101
Cr-Commit-Position: refs/heads/master@{#291679}

[csharp, 2014-08-22 18:12:20]

I don't think this will fix the issue in the bug, but it does have the potential
to fix some bad interactions.

[robertshield, 2014-08-25 13:40:18]

https://codereview.chromium.org/500563002/diff/1/chrome_elf/blacklist/blackli...
File chrome_elf/blacklist/blacklist.cc (left):

https://codereview.chromium.org/500563002/diff/1/chrome_elf/blacklist/blackli...
chrome_elf/blacklist/blacklist.cc:90: if (blacklist_state ==
blacklist::BLACKLIST_SETUP_RUNNING) {
previously, BLACKLIST_STATE_FAILED would hit this branch (and return false) as
well. Just double checking that the fact that it now doesn't and will return
true instead is intentional.

[robertshield, 2014-08-25 13:45:08]

as discussed, lgtm

[csharp, 2014-08-25 13:45:15]

The CQ bit was checked by csharp@chromium.org

[commit-bot: I haz the power, 2014-08-25 13:45:38]

CQ is trying da patch. Follow status at
 https://chromium-status.appspot.com/cq/csharp@chromium.org/500563002/1

[commit-bot: I haz the power, 2014-08-25 14:38:07]

Committed patchset #1 (1) as 3de54bf82c5df15d9a587af10165cc7d7121ed30

[commit-bot: I haz the power, 2014-09-10 02:34:25]

Patchset 1 (id:??) landed as
https://crrev.com/619b85aaed93f95207dc9c06fa85fe14cb91c101
Cr-Commit-Position: refs/heads/master@{#291679}