Expose message grid from ServiceInsight in ServicePulse

[PhilBastian]

Describe the feature.

This issue is for exposing the message audit functionality in ServicePulse, currently only accessible in ServiceInsight.

Note: this issue is for the grid functionality only. Individual message details and functionality are covered in other issues

Requirements

• Retrieve messages from ServiceControl http://servicecontrolurl/api/messages/
  • NOTE: This endpoint returns both failures and successes as part of an audit trail. The failures are also visible in the failed messages tab which allows for all failures to be grouped and batched retried.
• Display messages details in a grid (i.e. HTML table, as per existing ServicePulse functionality)
  • Columns to be shown:
    • Status (Icon, not text, see below)
    • Message Id
    • Message Type
    • Time Sent
    • Processing Time
    • 
  • Sortable on all columns
  • Paginated (server-side pagination)
  • Refresh manual only by default, option to have it automated (performance implications)
• Selecting a row will route to the audit message details screen, similar to existing functionality for failed messages at /failed-messages/message/messageId
  • Similar to Failed Messages screen
    • Message Type
    • Sent Timelapsed
    • Endpoint
    • Host
    • TabControl (NOTE: each tab should not be visible until the issue its respective contents is completed):
      • Properties
      • Headers
      • Body
      • Flow Diagram
      • Saga Diagram
      • Sequence Diagram
  • This screen should also have the Open in ServiceInsight button as per the functionality for failed messages. This will assist with filling in "missing" functionality while waiting for remaining ServiceInsight functionality to be migrated.
• There is no requirement for bulk selection of rows, or actions to be performed on a row/rows from this screen

Some care should be taken to incorporate allowances for future functionality. This can be imagined as similar to the current failed messages drill-down screen for an individual message.

Additional Context

No response