GitLab

This reverts commit 524d9990.

Reason for revert:
Multiple developers were unable to launch lacros, due to using
@managedchrome.com or @chromium.org accounts for testing.

Until we can revisit the policy settings for common domains used
by developers, I'm going to revert.

Original change's description:
> lacros: Allow LacrosAllowed policy to apply to developer builds
>
> Clean up some leftover logic from when we disabled lacros in M87 for
> non-google managed users. In particular, don't skip the policy check
> for developer builds with channel unknown. The LacrosAllowed pref
> defaults to true, so this doesn't affect developers who aren't working
> with policy.
>
> Bug: 1135494
> Test: updated unit_tests
> Change-Id: I510ada8de5d266626ba8adef64a7dd33202574a8
> Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2628592
> Reviewed-by: Igor <igorcov@chromium.org>
> Commit-Queue: James Cook <jamescook@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#844259}

TBR=jamescook@chromium.org,igorcov@chromium.org,chromium-scoped@luci-project-accounts.iam.gserviceaccount.com

# Not skipping CQ checks because original CL landed > 1 day ago.

Bug: 1135494
Change-Id: Ice9c8695697c3362dc4170410752484e0ff05f28
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2640644Reviewed-by: James Cook <jamescook@chromium.org>
Commit-Queue: James Cook <jamescook@chromium.org>
Cr-Commit-Position: refs/heads/master@{#845359}