GitLab

This way, chrome should be able to set up user keystone
on first run in most cases.

Also don't offer installation if /Applications/Google Chrome.app already
exists.

BUG=128462
TEST=
1.) Run as user.
Have chrome with system ticket and user keystone installed anywhere.
  -> Shouldn't offer installation.
Have chrome with user ticket and user keystone installed anywhere.
  -> Shouldn't offer installation.

Have chrome with system ticket and system keystone installed anywhere.
  -> Shouldn't offer installation.
Have chrome with system ticket and system keystone installed anywhere.
  -> Shouldn't offer installation.

Have chrome in /Applications, no matter owned by whom and no matter
if with keystone set up.
  -> Shouldn't offer installation.

Don't have chrome installed
  -> Offers to install, and creates /Applications/Google Chrome.app which
    is owned by the current user. On first launch, Chrome registers itself
    successfully for a user ticket without user interaction.

2.) Same as with 1, but run as root. Should have EXACTLY the same results,
i.e. chrome is still installed as current user, and when run as the current
user (not root) successfully registers itself.

Review URL: https://chromiumcodereview.appspot.com/10834102

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@151324 0039d316-1c4b-4281-b951-d872f2087c98