In-app messaging to communicate the imminent 32-bit deprecation to 32-bit-only users

In-app messaging to communicate the imminent 32-bit deprecation to 32-bit-only
users.

In Google Chrome-branded builds, show an infobar at startup to users with
32-bit-only systems, and add a message to the about page for those users
advising that automatic updates will soon stop because the system
configuration is about to become unsupported.

A provision is made to change this message to an "end-of-the-line" message for
the final 32-bit-compatible build. When this switch is flipped, the autoupdate
status and promotion button on the about page will be hidden. The
"end-of-the-line" message will appear there, alongside the icon normally used
for failed updates. The startup infobar text will change at that point as
well.

No observable changes for non-branded Chromium builds (since they're not
receiving updates through this mechanism) or for users with 64-bit-capable
systems (because they're not being obsoleted).

R=arv@chromium.org, thakis@chromium.org, thakis
BUG=303280, 331810, 331830
Committed: https://src.chromium.org/viewvc/chrome?view=rev&revision=245598

[Mark Mentovai, 2014-01-06 22:10:15]

I’m done with most of the work here except for the strings and URL, but I’m
still going to wait to check this in until we’re positive about it. But I’d
still appreciate a review.

[Nico, 2014-01-07 00:51:37]

lgtm

https://codereview.chromium.org/125443002/diff/30001/chrome/app/chromium_stri...
File chrome/app/chromium_strings.grd (right):

https://codereview.chromium.org/125443002/diff/30001/chrome/app/chromium_stri...
chrome/app/chromium_strings.grd:353: This computer will soon stop receiving
updates of Chromium because its processor is outdated.
Should this contain "32 bit" somewhere?

https://codereview.chromium.org/125443002/diff/30001/chrome/browser/mac/syste...
File chrome/browser/mac/system_bitness.h (right):

https://codereview.chromium.org/125443002/diff/30001/chrome/browser/mac/syste...
chrome/browser/mac/system_bitness.h:11: namespace chrome {
I thought stuff in chrome/ isn't in a namespace (?)

[Mark Mentovai, 2014-01-07 17:55:38]

https://codereview.chromium.org/125443002/diff/30001/chrome/app/chromium_stri...
File chrome/app/chromium_strings.grd (right):

https://codereview.chromium.org/125443002/diff/30001/chrome/app/chromium_stri...
chrome/app/chromium_strings.grd:353: This computer will soon stop receiving
updates of Chromium because its processor is outdated.
Nico wrote:
> Should this contain "32 bit" somewhere?

Maybe. I’m using bug 331830 to try to get the actual text figured out.

[Mark Mentovai, 2014-01-07 19:32:23]

+arv for chrome/browser/ui/webui and chrome/browser/resources.

[Mark Mentovai, 2014-01-09 16:50:40]

Strings updated per bug 331830.

[arv (Not doing code reviews), 2014-01-09 19:06:07]

js,html,grd LGTM

[Mark Mentovai, 2014-01-10 21:33:00]

This change is still held up waiting for a help center doc, so I broke the
unrelated part about the uninitialized variable for the promote button out into
its own change, https://codereview.chromium.org/131933003/ .

[Mark Mentovai, 2014-01-17 20:30:54]

Committed patchset #10 manually as r245598 (presubmit successful).