ProfileManager doesn't depend on "--login-profile" switch.

Chrome OS doesn't treat value of "login-profile" as a name
for user's profile dir anymore, however ProfileManager used its
value to let some old tests keep working. After removal
"login-profile" from ProfileManager these tests were fixed.

The significant change is that
TestingProfileManager::CreateTestingProfile treats its
|profile_name| argument as an user's id on CrOS, and creates
profile with a correct path ("u-" +
user_id_hash(profile_name)). This makes testing environment
closer to real, so communication between ProfileManager <-->
chromeos::ProfileHelper <--> chromeos::UserManager works
without additional set up in tests.

BUG=294628
TEST=all browser_tests and unit_tests are passing

Review URL: https://codereview.chromium.org/442043002

Cr-Commit-Position: refs/heads/master@{#291895}
Disable lock if no credentials are present

BUG=335086
TEST=Ensure new-profile-management and account-consistency are not
enabled. Then sign in a profile. Then enable new-profile-management.
The "lock" button of the avatar menu should be present but disabled.

Review URL: https://codereview.chromium.org/497783002

Cr-Commit-Position: refs/heads/master@{#291896}
Roll gyp r1967:1970.

r1970 android: Support host multilib builds.
r1969 Makes analyzer output names of all executable target types
r1968 android: Make buildbot able to use a custom manifest.

BUG=

Review URL: https://codereview.chromium.org/502393002

Cr-Commit-Position: refs/heads/master@{#291897}
DevTools: Test for disabling PortForwardingController

BUG=407137

Review URL: https://codereview.chromium.org/503763002

Cr-Commit-Position: refs/heads/master@{#291898}
Move deduping_factory files.

BUG=352290

Review URL: https://codereview.chromium.org/499383002

Cr-Commit-Position: refs/heads/master@{#291899}
Remove old Aura Gesture Detection Pipeline.

I'll file separate bugs for the additional cleanup this enables.

BUG=332418

Review URL: https://codereview.chromium.org/458363002

Cr-Commit-Position: refs/heads/master@{#291900}
Removes usage of aura::Window from Node

Each Node no longer creates an aura::Window. Instead RootViewManager
creates a single aura::Window that is responsible for drawing the
entire scene. RootViewManager is told when to redraw certain
areas. When RootViewManager needs to paint is paints the whole
tree.

At some point RootViewManager won't creat an aura::Window at all,
instead it'll take to the surface manager and create the frame data
for the scene.

BUG=none
TEST=none
R=jamesr@chromium.org

Review URL: https://codereview.chromium.org/507563002

Cr-Commit-Position: refs/heads/master@{#291901}
Add ManagePasswordsBubbleNeverSaveViewController and unit tests.

BUG=328847

Review URL: https://codereview.chromium.org/450643003

Cr-Commit-Position: refs/heads/master@{#291902}
Combine MSVS warning supression codes
together in crypto.gyp

"msvs_disabled_warnings" code definition present in two place in the same 'target_name': 'crypto'.

Review URL: https://codereview.chromium.org/492963004

Cr-Commit-Position: refs/heads/master@{#291903}
linux: Always use (64bit) gold for linking, even on 32bit.

All 32bit bots now have 64bit kernels and can run 64bit gold. So always use
that.  We already require running 64bit binaries for clang, and the official
bots already used to do this for gold.  This makes linking on 32bit bots faster,
and simplifies our configurations.

BUG=396333
TBR=brettw

Review URL: https://codereview.chromium.org/503873004

Cr-Commit-Position: refs/heads/master@{#291904}
Revert of linux: Always use (64bit) gold for linking, even on 32bit. (patchset #3 of https://codereview.chromium.org/503873004/)

Reason for revert:
Tentatively reverting because it made the sizes bot grumpy (http://build.chromium.org/p/chromium/buildstatus?builder=Linux&number=52715)

Original issue's description:
> linux: Always use (64bit) gold for linking, even on 32bit.
>
> All 32bit bots now have 64bit kernels and can run 64bit gold. So always use
> that.  We already require running 64bit binaries for clang, and the official
> bots already used to do this for gold.  This makes linking on 32bit bots faster,
> and simplifies our configurations.
>
> BUG=396333
> TBR=brettw
>
> Committed: https://chromium.googlesource.com/chromium/src/+/c7864673b16236a2ec3cd435bb11608cbb76c1b4

TBR=thestig@chromium.org,brettw@chromium.org,thakis@chromium.org
NOTREECHECKS=true
NOTRY=true
BUG=396333

Review URL: https://codereview.chromium.org/482173003

Cr-Commit-Position: refs/heads/master@{#291905}
Creates CacheContext for ServiceWorkerCacheStorage.

Creates CacheContext which the CacheStorage uses to keep track of
Cache metadata rather than sticking it in the ServiceWorkerCache where
it doesn't belong.  The CacheContext will be used in a downstream CL
to keep reference count information for each cache.

This CL also changes the CacheMap from an IDMap to a std::map with our own id counting.
This lets us change to int64 from int32 as well as helps the transition to reference counting the caches.

Some other upcoming CLs affecting CacheStorage:
* Reference count CacheContext so that the deletion of javascript objects can delete the ServiceWorkerCache
* Make the callbacks in ServiceWorkerCacheStorage unnamed functions that don't require weak pointers.
* Change the CacheID to int64.

BUG=392621

Review URL: https://codereview.chromium.org/503823002

Cr-Commit-Position: refs/heads/master@{#291906}
Revert of Suppress an uninitialized value in KeyboardLayoutManager::SetChildBounds. (patchset #1 of https://codereview.chromium.org/502183003/)

Reason for revert:
https://codereview.chromium.org/480723006/ fixed this.

Original issue's description:
> Suppress an uninitialized value in KeyboardLayoutManager::SetChildBounds.
>
> BUG=407467
> TBR=bshe@chromium.org
>
> Committed: https://chromium.googlesource.com/chromium/src/+/1598e5ab15e3c24f6d17e2214e61185d1098c915

TBR=bshe@chromium.org
NOTREECHECKS=true
NOTRY=true
BUG=407467

Review URL: https://codereview.chromium.org/506953002

Cr-Commit-Position: refs/heads/master@{#291907}
Prevent the screen from sleeping when the desktop is being captured.

BUG=405784

Review URL: https://codereview.chromium.org/502103003

Cr-Commit-Position: refs/heads/master@{#291908}
Fix issues caused due to GitMigration.

BUG=
NOTRY=True

Review URL: https://codereview.chromium.org/503283002

Cr-Commit-Position: refs/heads/master@{#291909}
cc: Do bitmap conversion for RasterBuffer in the worker thread.

- Moved RasterBuffer from ResourceProvider to its own file.
It's now the public interface used by raster tasks.
- Added Acquire/ReleaseSkCanvas() interface into
RasterBuffer.
- Bitmap conversion is now done in raster worker thread
through RasterBuffer interface.

BUG=None

Review URL: https://codereview.chromium.org/454843002

Cr-Commit-Position: refs/heads/master@{#291910}
Update expectations for generate_resources_map_unittest.py.

This makes the test pass.

BUG=none

Review URL: https://codereview.chromium.org/500223002

Cr-Commit-Position: refs/heads/master@{#291911}
Fix Cronet compilation and test errors.

- Use UrlRequestContext.CreateRequest.
- Expect GIT revision in HttpUrlRequestFactoryTest.
- Prevent getAllHeaders from being removed by proguard.

BUG=390267

Review URL: https://codereview.chromium.org/500193002

Cr-Commit-Position: refs/heads/master@{#291912}
Revert of Move BrowserWindowPropertyManager tests to interactive_ui_tests and reenable. (patchset #1 of https://codereview.chromium.org/492623003/)

Reason for revert:
Causing huge amounts of flake even with retries, see these jobs that failed on the CQ.

Please don't renable without watching the trybots closely to make sure it's not causing a lot of failures: http://build.chromium.org/p/tryserver.chromium.win/builders/win_chromium_rel_swarming?numbuilds=200

http://build.chromium.org/p/tryserver.chromium.win/builders/win_chromium_rel_swarming/builds/5716
http://build.chromium.org/p/tryserver.chromium.win/builders/win_chromium_rel_swarming/builds/5716
http://build.chromium.org/p/tryserver.chromium.win/builders/win_chromium_rel_swarming/builds/5696
http://build.chromium.org/p/tryserver.chromium.win/builders/win_chromium_rel_swarming/builds/5688
http://build.chromium.org/p/tryserver.chromium.win/builders/win_chromium_rel_swarming/builds/5685
http://build.chromium.org/p/tryserver.chromium.win/builders/win_chromium_rel_swarming/builds/5680
http://build.chromium.org/p/tryserver.chromium.win/builders/win_chromium_rel_swarming/builds/5678
http://build.chromium.org/p/tryserver.chromium.win/builders/win_chromium_rel_swarming/builds/5675
http://build.chromium.org/p/tryserver.chromium.win/builders/win_chromium_rel_swarming/builds/5673
http://build.chromium.org/p/tryserver.chromium.win/builders/win_chromium_rel_swarming/builds/5671
http://build.chromium.org/p/tryserver.chromium.win/builders/win_chromium_rel_swarming/builds/5667
http://build.chromium.org/p/tryserver.chromium.win/builders/win_chromium_rel_swarming/builds/5666
http://build.chromium.org/p/tryserver.chromium.win/builders/win_chromium_rel_swarming/builds/5665
http://build.chromium.org/p/tryserver.chromium.win/builders/win_chromium_rel_swarming/builds/5663
http://build.chromium.org/p/tryserver.chromium.win/builders/win_chromium_rel_swarming/builds/5661
http://build.chromium.org/p/tryserver.chromium.win/builders/win_chromium_rel_swarming/builds/5661
http://build.chromium.org/p/tryserver.chromium.win/builders/win_chromium_rel_swarming/builds/5660
http://build.chromium.org/p/tryserver.chromium.win/builders/win_chromium_rel_swarming/builds/5647
http://build.chromium.org/p/tryserver.chromium.win/builders/win_chromium_rel_swarming/builds/5644
http://build.chromium.org/p/tryserver.chromium.win/builders/win_chromium_rel_swarming/builds/5643
http://build.chromium.org/p/tryserver.chromium.win/builders/win_chromium_rel_swarming/builds/5637
http://build.chromium.org/p/tryserver.chromium.win/builders/win_chromium_rel_swarming/builds/5639

Original issue's description:
> Move BrowserWindowPropertyManager tests to interactive_ui_tests and reenable.
>
> This test was flaky because it modified system properties. Moving it to
> interactive_ui_tests should allow it the system control guarantees it
> needs to complete successfully.
>
> BUG=396344
>
> Committed: https://chromium.googlesource.com/chromium/src/+/4d5d5d700a104f5e6bec47a8891fc5a54a4f242b

TBR=sky@chromium.org,calamity@chromium.org
NOTREECHECKS=true
NOTRY=true
BUG=396344

Review URL: https://codereview.chromium.org/504253002

Cr-Commit-Position: refs/heads/master@{#291913}
[Telemetry] Disable failing smoothness.simple_mobile_sites benchmark.

This patch should be reverted when it is fixed along with a unittest to
guard against regression.

BUG=402885
NOTRY=True
TBR=epenner@chromium.org

Review URL: https://codereview.chromium.org/504163003

Cr-Commit-Position: refs/heads/master@{#291914}