Build all Crashpad tests in Chromium, and run on Chromium bots

Originally landed at efd8584f0232
(https://chromium-review.googlesource.com/751403) and subsequently
reverted at 49f5374a36de because of test failures. There are no changes
to this reland, but the test failures are addressed by updating Crashpad
to include
https://chromium.googlesource.com/crashpad/crashpad/+/d3b7463c7a48.

Until the recent ef647b4938a6 and 00a065492978, Crashpad tests did not
build or run in Chromium. Since then, crashpad_util_test was buildable
in Chromium, but was only run on Windows bots.

Crashpad has many more tests than crashpad_util_test, and its tests run
on both macOS and Windows. This change allows all of Crashpad’s unit
tests to build in Chromium’s GN-based build, and runs them on macOS and
Windows try- and buildbots.

Rather than having individual module-specific test executables like
crashpad_util_test, all unit tests are brought together into one
monolithic “crashpad_tests” executable.

On Windows, Crashpad also has an “end_to_end_test.py” which drives
crashpad_handler and some test crasher programs, and verifies the
produced minidump output by running the cdb debugger. That’s not
currently accounted for in the Chromium build.

As part of this change, additional Crashpad tools are also added to the
Chromium build, including the generate_dump tool.

Bug: 779790, 782011
Change-Id: Id192c40a1e7db178bdb093cd050b7fc5a5a876c9
Reviewed-on: https://chromium-review.googlesource.com/757188
Commit-Queue: Mark Mentovai <[email protected]>
Reviewed-by: Sigurður Ásgeirsson <[email protected]>
Reviewed-by: Dirk Pranke <[email protected]>
Cr-Commit-Position: refs/heads/master@{#514759}
18 files changed