GitLab

This feature has now rolled out to stable, so we change the default of
the feature to enabled, allowing us to remove the .gcl file when M87 is
promoted to Stable.

Because serious/critical thermal signals are so rare (<1% of macOS
population) and the impact of this resource is little-to-none, an
alternative would be to simply delete the ThermalResource.

However, by keeping the code, if the macOS signal is improved in a
future release or if the thermal resource becomes available on more
platforms (there are WIP CLs on Android and ChromeOS) then having the
ThermalResource will automatically make use of these signals. And by
having the base::Feature still in here, if changes to OS signals were
to cause any regressions, we can use it as a kill-switch.

// TBR in place of Evan's +1 (he's not a committer yet).
TBR=guidou@chromium.org

Bug: chromium:1100336
Change-Id: I03a2a765bd4b8cbbca5a9b618c71d7214b830ce6
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2418335Reviewed-by: Henrik Boström <hbos@chromium.org>
Commit-Queue: Henrik Boström <hbos@chromium.org>
Cr-Commit-Position: refs/heads/master@{#808843}