feat(taskworker): Make ingest errors taskworker compatible

[enochtangg]

This work is required to migrate tasks from celery to the new taskbroker system. The sentry option will be used to control the rollout of these tasks. The full migration plan is describe in this document.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

✅ All tests successful. No failed tests found.

Additional details and impacted files

@@            Coverage Diff             @@
##           master   #90340      +/-   ##
==========================================
- Coverage   87.78%   85.22%   -2.56%     
==========================================
  Files       10276    10288      +12     
  Lines      582704   583825    +1121     
  Branches    22567    22658      +91     
==========================================
- Hits       511543   497584   -13959     
- Misses      70732    85695   +14963     
- Partials      429      546     +117     

[evanh]

All of these tasks have untyped parameters (in some cases just **kwargs). I think we should do some extra auditing to try and ensure that all the parameters these functions are called with can be serialized to JSON.

[enochtangg]

@evanh Just did an audit. It looks like post_process_group is the only task that calls with kwargs. Its parameters are safe to serialize with JSON

[evanh]

This looks good to me but I wouldn't name this INGEST, I think this is a concept we could use for other namespaces besides ingest that receive high traffic.

[markstory]

Looks good, the extra settings will help prevent another option problem.