Accept non-fatal resource exceptions without generating crash reports

Accept non-fatal resource exceptions without generating crash reports.

This adds IsExceptionNonfatalResource() and its test, and uses it in
crashpad_handler. When non-fatal resource exceptions are encountered, no
crash report is generated. crashpad_handler swallows these exceptions.
Alternatively, it could allow them to be sent to the system’s host-level
resource exception handler, normally com.apple.ReportCrash.root, which
would allow them to be processed in the same way as when Crashpad is not
in use. I’m not sure which option is better. I chose to swallow them
because there doesn’t appear to be much value in letting
com.apple.ReportCrash.root and spindump look at them.

This also moves ExcCrashRecoverOriginalException() to the new file as a
sibling of IsExceptionNonfatalResource(). This provides better
organization.

BUG=crashpad:35, chromium:474163, chromium:474326
TEST=crashpad_util_test ExceptionTypes.IsExceptionNonfatalResource
R=rsesek@chromium.org

Committed: https://chromium.googlesource.com/crashpad/crashpad/+/1baff4ff92fe1a1ead6b88b5f01633a4f0b6b51c

[Mark Mentovai, 2015-04-07 22:38:55]

mark@chromium.org changed reviewers:
+ rsesek@chromium.org

[Mark Mentovai, 2015-04-08 13:54:51]

Patchset #3 (id:40001) has been deleted

[Robert Sesek, 2015-04-08 21:42:24]

LGTM. Are you not handling EXC_GUARD the same way?

[Mark Mentovai, 2015-04-08 21:42:48]

EXC_GUARD is always fatal.

[Mark Mentovai, 2015-04-08 21:46:14]

Committed patchset #4 (id:80001) manually as
1baff4ff92fe1a1ead6b88b5f01633a4f0b6b51c (presubmit successful).