GitLab

When kStubCrosSettings switch is set, the logged in user is treated
as the owner of the device, and of the stubbed settings (which don't
need a real owner key).

This change moves this promotion of the user to the owner out of
ChromeUserManagerImpl and into CrosSettings. This untangles the two
classes slightly, and also it means that we can get rid of one
call to CrosSettings->Set, which is being removed.

See go/writepath for more background

Bug: 433840
Change-Id: I9f4a34b34d0160d220558e512b9d1c56b3e253a1
Reviewed-on: https://chromium-review.googlesource.com/c/1314491Reviewed-by: Steven Bennetts <stevenjb@chromium.org>
Commit-Queue: A Olsen <olsen@chromium.org>
Cr-Commit-Position: refs/heads/master@{#604937}