Add DumpWithoutCrashing when mojo read reasult is INVALID_ARGUMENT

The previous CL (crrev.com/c/5385205) tols us the unexpected mojo result
code is MOJO_RESULT_INVALID_ARGUMENT. We're not sure why this is
returned so far.

This CL adds DumpWithoutCrashing() and some crash keys to
monitor so that we get more clarity on why mojo ReadData returns
MOJO_RESULT_INVALID_ARGUMENT.

Unresolved-Comment-Reason: We close remaining discussion after the investigation, and that can be done in a separate CL.
Bug: 1472634
Change-Id: I14b4f6cdf2a42b0f8456dcf4c67c18db1d9cffd4
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5404611


Reviewed-by: Minoru Chikamune <chikamune@chromium.org>
Commit-Queue: Shunya Shishido <sisidovski@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1280064}