[ENH] handle panics in query service

[codetheweb]

This PR adds a test to confirm Tonic handles panics in the simplest cases for the query node.

Panics within components are untested (I suspect they wouldn't be caught by this).

[github-actions]

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)

[codetheweb]

suggestions welcome for a cleaner way to do this, I just want a way to trigger a panic within a service from a test

[HammadB]

It this just so when testing manually you can check its up?

[codetheweb]

I need a handler that returns a successful response without panicking. Alternatively I could add a shoud_panic option to the request for TriggerPanic, or call a normal rpc route like QueryVectors

[HammadB]

Got it, thats fine makes sense

[HammadB]

Makes sense, just a nit on comments. Are we adding the panic hook in another PR?

[codetheweb]

Are we adding the panic hook in another PR?

yep 👍