Disable ContentVerifier when FakeCWS is used

Current implementation of FakeCWS doesn't support signed hashes for
extensions' resources. Therefore content verification of extensions
provided by FakeCWS may fail and extensions will be false-positively
marked as corrupted. This commit disables content verification when
FakeCWS is used, as we don't need it in corresponding tests.

Also this commit removes condition when overriding WebStore URLs for
ExtensionsClient, now they are always updated. That condition only added
possible flakiness. In tests ExtensionsClient was initialized after
command line changes, so it used overridden values anyway.

Bug: 1051513
Change-Id: Ie74553f6f778efa0e82f17f64149d688e320f151
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2051931
Commit-Queue: Anatoliy Potapchuk <apotapchuk@chromium.org>
Reviewed-by: Anatoliy Potapchuk <apotapchuk@chromium.org>
Reviewed-by: Roman Sorokin [CET] <rsorokin@chromium.org>
Cr-Commit-Position: refs/heads/master@{#741446}
2 files changed