Add Op Context To Runtime Error Messages

[kkloberdanz]

A recent error message that I encountered when running a compiled computation was missing information such as on which op did the error occur. By adding some more information to our error messages, it will help debugging runtime errors.

A possible follow up ticket would be to also provide the Python line number of where the error happened in the Python EDSL script.

Error message in question:

Traceback (most recent call last):
  File "/home/kyle/src/maestro/computation/aes_lin_reg_predict.py", line 122, in <module>
    serialize_edsl_computation(
  File "/home/kyle/src/maestro/computation/aes_lin_reg_predict.py", line 107, in serialize_edsl_computation
    result = runtime.evaluate_compiled(
  File "/home/kyle/src/runtime/pymoose/pymoose/testing.py", line 39, in evaluate_compiled
    return super().evaluate_compiled(comp_bin, role_assignment, arguments)
RuntimeError: Test runtime error: Type mismatch, expected HostBitTensor but found HostFloat64Tensor