bug-1918240: Add crash_inconsistencies field from rust-minidump

[relud]

from :btsoi in bug-1918240:

Rust-minidump has added a feature for detecting inconsistent crashes (see the crash_inconsistencies field in the JSON Schema). It will be helpful to show this on crash-stat to indicate that the crash doesn't make sense and is likely caused by bad hardware.
I think it probably makes sense to treat the field similar to bitflips and have the following support:

• make it publicly viewable
• add it to the Details tab in the report view
• make it searchable in Super Search
• make it aggregatable in Super Search and Signature report

[smarnach]

This looks good to me, but I'm not really familiar with this codebase. Here are a couple of questions I can't answer:

• Do we really need CrashInconsistenciesRule, or is there some other mechanism that can handle trivial cases like this one? Can this possibly be done by CopyFromRawCrashRule?
• If we need the rule, what file in the socorro/processor/rules directory should it go in?

I presume you know the answers and did everything correctly, so I'll approve. :)

[relud]

* Do we really need `CrashInconsistenciesRule`, or is there some other mechanism that can handle trivial cases like this one? Can this possibly be done by `CopyFromRawCrashRule`?

creating a new rule was suggested by @willkg via zoom when he was explaining how to do this, so I'm going to take that as confirmation a new rule is the right way to go here.

* If we need the rule, what file in the socorro/processor/rules directory should it go in?

I'm confident this should go in breakpad.py because the data source is rust-minidump and all other data generated specfically in that package is handled by rules in that file.