Reprocessed events are not queryable/accessible via activity

### Environment

SaaS (https://sentry.io/)

### Steps to Reproduce

1. From the issue actions overflow menu, select 'Reprocess Events'
2. After the reprocessing finishes, a new activity should appear marking X events as reprocessed with a link.
3. Click the link, and observe an empty issue stream query

### Expected Result

Clicking the link should show the new issue with reprocessed events attached. The query is `reprocessing.original_issue_id:X`, which should return results even if it was typed in manually.

### Actual Result

The query will always return empty because the search field parser does not know anything about this `reprocessing.original_issue_id` field.

In my investigation there are a few steps we need to accomplish to get this working:

- Tests indicate that the reprocessing data is appended as a context called `reprocessing` and a key on that context of `original_issue_id`. This should be verified to still be the case today.
- After that, the field needs to be exposed to the search parser somehow. Context is not usually indexed for search, but I know we make exceptions for certain items such as `user` or `browser`. I'm not sure at which stage this occurs and if we can do it dynamically, so this might have to get done when we save the new events as a part of reprocessing.
- Lastly, if the field is recognized, we can expose the field to the frontend as a filter option for autocomplete (the same way is done for a project's common tag keys or values)

### Product Area

Issues

### Link

_No response_

### DSN

_No response_

### Version

_No response_