[ENH] catch panics in tasks

[codetheweb]

This catches panics when they occur inside dispatched tasks, preventing the associated worker component from crashing. Depending on upstream handling this can still result in a component crashing--many places use .unwrap() instead of handling errors.

I originally started down the route of adding lifecycle events to components, but after talking with @Ishiihara we decided that the complexity tradeoff may not be worth it right now, and catching panics at the task level is quite a bit easier. (Unlike components, tasks have the concept of a request/response unit, so it's much easier to propagate the error.)

If something panics outside a task, e.g. logic in an orchestrator, the query node will survive as Tonic catches it. The only other place we have to worry about are panics in the CompactionManager/CompactOrchestrator which can be handled separately.

[github-actions[bot]]

Reviewer Checklist

Please leverage this checklist to ensure your code review is thorough before approving

Testing, Bugs, Errors, Logs, Documentation

• [ ] Can you think of any use case in which the code does not behave as intended? Have they been tested?
• [ ] Can you think of any inputs or external events that could break the code? Is user input validated and safe? Have they been tested?
• [ ] If appropriate, are there adequate property based tests?
• [ ] If appropriate, are there adequate unit tests?
• [ ] Should any logging, debugging, tracing information be added or removed?
• [ ] Are error messages user-friendly?
• [ ] Have all documentation changes needed been made?
• [ ] Have all non-obvious changes been commented?

  System Compatibility

• [ ] Are there any potential impacts on other parts of the system or backward compatibility?
• [ ] Does this change intersect with any items on our roadmap, and if so, is there a plan for fitting them together?

  Quality

• [ ] Is this code of a unexpectedly high quality (Readability, Modularity, Intuitiveness)

[HammadB]

If we add a standard reply type to Components in System (which we have wanted to do) can't we get this for free here?

I'd somewhat prefer that as it is more widely usable as this is built on top of system components. Wdyt?

If that is seen as too much rn I'd be ok with taking this tech debt if seen that way (I have some minor ergonomics comments if so)

[codetheweb]

If we add a standard reply type to Components in System (which we have wanted to do) can't we get this for free here?

I would prefer this, I didn't realize it was something planned. I'll take a look.