GitLab

This CL moves the API and implementation via which devtools enables
forced activation of the subresource filter from //chrome to
//components. This move will enable easy reuse of this logic by WebLayer
in a followup CL. In this CL there is no behavioral change.

The relevant unittests are also ported from //chrome to //components.
It was not possible to port a test of the interaction with content
settings, as that interaction is //chrome-level. However, that check
(that content settings is updated when the component declares to the
client that the page is activated) is covered by other tests in
//chrome's subresource_filter_unittest.cc.

Bug: 1116095
Change-Id: Ia9126e445738d22b4e666515475d5da57dbd6eeb
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2587057
Commit-Queue: Colin Blundell <blundell@chromium.org>
Reviewed-by: Charlie Harrison <csharrison@chromium.org>
Cr-Commit-Position: refs/heads/master@{#838010}