Improve Interrupted status messages

[sabbyanandan]

Context:

need to see a log feed of webhook calls to see which one failed so one can act upon it.

Similar to the line item at #324 (comment), it'd be helpful for developers to know what is the cause/reason for the failure in its raw log format, including the timestamp.

Additionally, today, we show high-level information when the developer hovers over, but when we have the raw log content, we can revisit the display of it from the DX perspective.

[MicaiahReid]

To flesh this out some more, I think the steps would be:

• Improve Interrupted status messages to be clear and actionable.
• Consider adding more raw error data to the status, maybe in another field on the below object
• Add context fields to erroring chainhooks:

{
  "error_msg": "...",
  "error_timestamp": "...",
  "last_evaluated_block_height": "...",
  "number_of_blocks_evaluated": "...",
  "number_of_times_triggered": "...",
  "last_occurrence": "..."
}

[MicaiahReid]

@sabbyanandan It may be helpful to release some sort of FAQ or doc for the users on how to resolve or act upon some the more common errors.

[smcclellan]

@MicaiahReid to fill in details for implementation.

[MicaiahReid]

I think the details I provided here should cover it! #528 (comment)