Support jumbo builds in the safe_browsing code (-6 CPU minutes)

Compiling the safe_browsing code is currently about 1% of the total
build effort in a jumbo build, and most of that effort can be
eliminated by adding support for jumbo in the safe_browsing code.

The gain would be a little bit bigger if the code hadn't been split
into a lot of 1-2 file targets. Those are not made jumbo since the
gain from merging just 2 files is limited, and merging just one file
makes no sense.

Bug: 927338
Change-Id: I0e8f57bdb1b39fc2f85a8adb4b00b3790d59d987
Reviewed-on: https://chromium-review.googlesource.com/c/1448455
Reviewed-by: Varun Khaneja <vakh@chromium.org>
Commit-Queue: Daniel Bratell <bratell@opera.com>
Cr-Commit-Position: refs/heads/master@{#628279}
2 files changed