Revert of Enable side-by-side beta and dev channels.

Revert of Enable side-by-side beta and dev channels. (patchset #5 id:100001 of https://codereview.chromium.org/2802713002/ )

Reason for revert:
Continuous builder test failure.

Original issue's description:
> Enable side-by-side beta and dev channels for Google Chrome.
> 
> This change introduces two new side-by-side channels for Google Chrome.
> Chrome Beta can be installed via the --chrome-beta installer command
> line switch, while Chrome Dev can be installed via the --chrome-dev
> switch. Such installs have the following qualities:
> 
> - They install in ...\Google\Chrome (Beta,Dev)\Application (both
>   per-machine and per-user installs are supported).
> - They store their User Data directories in %LOCALAPPDATA%\Google\Chrome
>   (Beta,Dev)\User Data.
> - They register with Google Update under distinct appguids:
>   - Beta: {8237E44A-0054-442C-B6B6-EA0509993955}
>   - Dev : {401C381F-E0DE-4B85-8BD8-3F3F14FBDA57}
> - Their shortcuts, taskbar, and Start Menu icons are badged with "Beta"
>   or "Dev", as appropriate.
> - While they will not prompt the user to be made the user's default
>   browser, they support being made such via the usual platform UX flows.
> - They self self-report as being on the "beta" and "dev" channels in
>   user metrics and crash reporting, respectively.
> 
> BUG=373987
> TEST=The test_installer build step covers general "will it blend"
> tests. Manual testing should verify such things as:
> - Does chrome://version show that the Executable and Profile paths
>   contain "Beta" or "Dev"?
> - Does chrome://version show "beta" or "dev" as the channel?
> - Do the shortcut and taskbar icons thave the proper badge?
> - Can these variations be installed alongside normal "Google Chrome"
>   with no interference?
> 
> Review-Url: https://codereview.chromium.org/2802713002
> Cr-Commit-Position: refs/heads/master@{#466436}
> Committed: https://chromium.googlesource.com/chromium/src/+/9897be5cb7fc7de9460c61e94eca2c4e27d99d8d

TBR=robertshield@chromium.org,thakis@chromium.org
# Skipping CQ checks because original CL landed less than 1 days ago.
NOPRESUBMIT=true
NOTREECHECKS=true
NOTRY=true
BUG=373987
Review-Url: https://codereview.chromium.org/2834973002
Cr-Commit-Position: refs/heads/master@{#466535}
Committed: https://chromium.googlesource.com/chromium/src/+/6f56a950ce7a91e149fbce18c3bd672f719dedb3

[grt (UTC plus 2), 2017-04-22 04:27:21]

The CQ bit was checked by grt@chromium.org

[grt (UTC plus 2), 2017-04-22 04:27:22]

Created Revert of Enable side-by-side beta and dev channels.

[commit-bot: I haz the power, 2017-04-22 04:27:26]

CQ is trying da patch.

Follow status at:
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[commit-bot: I haz the power, 2017-04-22 04:28:26]

CQ is committing da patch.

Bot data: {"patchset_id": 1, "attempt_start_ts": 1492835241531840, "parent_rev":
"bda3d4871655a1cb5121cde488845d9b968eda6c", "commit_rev":
"6f56a950ce7a91e149fbce18c3bd672f719dedb3"}

[commit-bot: I haz the power, 2017-04-22 04:29:37]

Description was changed from

==========
Revert of Enable side-by-side beta and dev channels. (patchset #5 id:100001 of
https://codereview.chromium.org/2802713002/ )

Reason for revert:
Continuous builder test failure.

Original issue's description:
> Enable side-by-side beta and dev channels for Google Chrome.
> 
> This change introduces two new side-by-side channels for Google Chrome.
> Chrome Beta can be installed via the --chrome-beta installer command
> line switch, while Chrome Dev can be installed via the --chrome-dev
> switch. Such installs have the following qualities:
> 
> - They install in ...\Google\Chrome (Beta,Dev)\Application (both
>   per-machine and per-user installs are supported).
> - They store their User Data directories in %LOCALAPPDATA%\Google\Chrome
>   (Beta,Dev)\User Data.
> - They register with Google Update under distinct appguids:
>   - Beta: {8237E44A-0054-442C-B6B6-EA0509993955}
>   - Dev : {401C381F-E0DE-4B85-8BD8-3F3F14FBDA57}
> - Their shortcuts, taskbar, and Start Menu icons are badged with "Beta"
>   or "Dev", as appropriate.
> - While they will not prompt the user to be made the user's default
>   browser, they support being made such via the usual platform UX flows.
> - They self self-report as being on the "beta" and "dev" channels in
>   user metrics and crash reporting, respectively.
> 
> BUG=373987
> TEST=The test_installer build step covers general "will it blend"
> tests. Manual testing should verify such things as:
> - Does chrome://version show that the Executable and Profile paths
>   contain "Beta" or "Dev"?
> - Does chrome://version show "beta" or "dev" as the channel?
> - Do the shortcut and taskbar icons thave the proper badge?
> - Can these variations be installed alongside normal "Google Chrome"
>   with no interference?
> 
> Review-Url: https://codereview.chromium.org/2802713002
> Cr-Commit-Position: refs/heads/master@{#466436}
> Committed:
https://chromium.googlesource.com/chromium/src/+/9897be5cb7fc7de9460c61e94eca...

TBR=robertshield@chromium.org,thakis@chromium.org
# Skipping CQ checks because original CL landed less than 1 days ago.
NOPRESUBMIT=true
NOTREECHECKS=true
NOTRY=true
BUG=373987
==========

to

==========
Revert of Enable side-by-side beta and dev channels. (patchset #5 id:100001 of
https://codereview.chromium.org/2802713002/ )

Reason for revert:
Continuous builder test failure.

Original issue's description:
> Enable side-by-side beta and dev channels for Google Chrome.
> 
> This change introduces two new side-by-side channels for Google Chrome.
> Chrome Beta can be installed via the --chrome-beta installer command
> line switch, while Chrome Dev can be installed via the --chrome-dev
> switch. Such installs have the following qualities:
> 
> - They install in ...\Google\Chrome (Beta,Dev)\Application (both
>   per-machine and per-user installs are supported).
> - They store their User Data directories in %LOCALAPPDATA%\Google\Chrome
>   (Beta,Dev)\User Data.
> - They register with Google Update under distinct appguids:
>   - Beta: {8237E44A-0054-442C-B6B6-EA0509993955}
>   - Dev : {401C381F-E0DE-4B85-8BD8-3F3F14FBDA57}
> - Their shortcuts, taskbar, and Start Menu icons are badged with "Beta"
>   or "Dev", as appropriate.
> - While they will not prompt the user to be made the user's default
>   browser, they support being made such via the usual platform UX flows.
> - They self self-report as being on the "beta" and "dev" channels in
>   user metrics and crash reporting, respectively.
> 
> BUG=373987
> TEST=The test_installer build step covers general "will it blend"
> tests. Manual testing should verify such things as:
> - Does chrome://version show that the Executable and Profile paths
>   contain "Beta" or "Dev"?
> - Does chrome://version show "beta" or "dev" as the channel?
> - Do the shortcut and taskbar icons thave the proper badge?
> - Can these variations be installed alongside normal "Google Chrome"
>   with no interference?
> 
> Review-Url: https://codereview.chromium.org/2802713002
> Cr-Commit-Position: refs/heads/master@{#466436}
> Committed:
https://chromium.googlesource.com/chromium/src/+/9897be5cb7fc7de9460c61e94eca...

TBR=robertshield@chromium.org,thakis@chromium.org
# Skipping CQ checks because original CL landed less than 1 days ago.
NOPRESUBMIT=true
NOTREECHECKS=true
NOTRY=true
BUG=373987

Review-Url: https://codereview.chromium.org/2834973002
Cr-Commit-Position: refs/heads/master@{#466535}
Committed:
https://chromium.googlesource.com/chromium/src/+/6f56a950ce7a91e149fbce18c3bd...
==========

[commit-bot: I haz the power, 2017-04-22 04:29:38]

Committed patchset #1 (id:1) as
https://chromium.googlesource.com/chromium/src/+/6f56a950ce7a91e149fbce18c3bd...