Bugzilla

I did a first round of reprocessing for crash reports >= 2023-08-01. We went from 51,320 to 7,232.

At Chris' behest, I did a second round of reprocessing for crash reports >= 2023-07-01 and < 2023-08-01. We went from 3,527 to 3,527--it looks like those weren't affected.

I did a first round of reprocessing for crash reports >= 2023-08-01. We went from 51,320 to 7,232.

Before:
```
$ supersearchfacet --signature='=EMPTY: no frame data available' --date='>=2023-08-01' \
    --_facets=product --format=markdown
```

product | count
------- | -----
Fenix | 50344
Focus | 947
ReferenceBrowser | 29
total | 51320

After:

```
$ supersearchfacet --signature='=EMPTY: no frame data available' --date='>=2023-08-01' \
    --_facets=product --format=markdown
```

product | count
------- | -----
Fenix | 7104
Focus | 127
ReferenceBrowser | 1
total | 7232

At Chris' behest, I did a second round of reprocessing for crash reports >= 2023-07-01 and < 2023-08-01. We went from 3,527 to 3,527--it looks like those weren't affected. 

```
$ supersearchfacet --signature='=EMPTY: no frame data available' --date='>=2023-07-01' --date='<2023-08-01' \
    --_facets=product --format=markdown
```

product | count
------- | -----
Fenix | 3493
Focus | 34
total | 3527

It looks like none of them have a `JavaStackTrace` or `JavaException`.

```
$ supersearch --signature='=EMPTY: no frame data available' --date='>=2023-07-01' --date='<2023-08-01' --num=all \
    | wc -l
3527
$ supersearch --signature='=EMPTY: no frame data available' --date='>=2023-07-01' --date='<2023-08-01' \
    --crash_report_keys=JavaStackTrace --crash_report_keys=JavaException --num=all \
    | wc -l
0
```