GitLab

In most places in the code we check both for the base::Feature
LacrosSupport and browser_util::IsLacrosAllowed(). In a recent code
review I forgot one. Move the feature check into IsLacrosAllowed()
and rename the function to IsLacrosEnabled().

This requires a small change to BrowserManager which also fixes a
bug. If enterprise policy switches from allowing Lacros to not
allowing Lacros we now clean up the binary in the component updater.
Previously the binary would stay there forever.

Follow-up to code review comment in:
https://chromium-review.googlesource.com/c/chromium/src/+/2542678

Bug: none
Test: manual, login with enterprise device, toggle flag
Test: added to unit_tests

Change-Id: I3938e6fed4af7831f41f947e9a30f03000f75cc1
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2547782
Auto-Submit: James Cook <jamescook@chromium.org>
Commit-Queue: Dominick Ng <dominickn@chromium.org>
Reviewed-by: Dominick Ng <dominickn@chromium.org>
Reviewed-by: Erik Chen <erikchen@chromium.org>
Reviewed-by: Ahmed Fakhry <afakhry@chromium.org>
Cr-Commit-Position: refs/heads/master@{#829028}