Properly create a new profile when the last non-supervised profile is deleted

Properly create a new profile when the last non-supervised profile is deleted
(even when it's not the current profile that's being deleted).

BUG=445043
Committed: https://crrev.com/ff3b4402237d177cc1cc57f8e44824dc3b2bd23a
Cr-Commit-Position: refs/heads/master@{#310751}

[Marc Treib, 2015-01-07 10:45:37]

treib@chromium.org changed reviewers:
+ noms@chromium.org

[Marc Treib, 2015-01-07 10:45:37]

PTAL!

[noms (inactive), 2015-01-08 21:13:22]

lgtm. 

This should only be different for supervised users, right? If you're deleting a
normal, secondary profile, then the last_non_supervised_profile_path won't be
empty, and everything will be the same?

[Marc Treib, 2015-01-09 10:13:37]

On 2015/01/08 21:13:22, Monica Dinculescu wrote:
> lgtm. 
> 
> This should only be different for supervised users, right? If you're deleting
a
> normal, secondary profile, then the last_non_supervised_profile_path won't be
> empty, and everything will be the same?

Yup. Actually, it should only be different when a supervised user deletes the
last non-supervised profile - all I've done here is move the "is this the last
non-supervised profile" check outside the "if (this is the current profile)".

[Marc Treib, 2015-01-09 10:13:52]

The CQ bit was checked by treib@chromium.org

[commit-bot: I haz the power, 2015-01-09 10:14:40]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/840733002/1

[commit-bot: I haz the power, 2015-01-09 10:53:35]

Committed patchset #1 (id:1)

[commit-bot: I haz the power, 2015-01-09 10:54:17]

Patchset 1 (id:??) landed as
https://crrev.com/ff3b4402237d177cc1cc57f8e44824dc3b2bd23a
Cr-Commit-Position: refs/heads/master@{#310751}