A long time ago, the processor would pass a raw_crash and a processed_crash into the Elasticsearch crash storage and then it would store entire sections of it after redacting the data by a set of forbidden / allowed keys.

We don't need to do that anymore. What we've got now is code that builds a crash document solely from processed crash data using a fields list specified in super_search_fields.py. It's explicit about what gets added. We no longer need Elasticsearch redactor infrastructure to handle forbidden / allowed keys.

This covers removing all that code.

I thought I could push this off until later, but this is tangled with bug #1697001 and that's tangled with the permissions changes I'm making. Given that, I think I can do this first, then bug #1697001 then go back to permissions changes.

willkg merged PR #6143: "bug 1784927: remove elasticsearch redactor code" in d16782f.

I deployed this to prod just now in bug #1787851. Marking as FIXED.