Saga diagram - first chunk of features

[cquirosj]

Features test covered:

• Feature: Detecting the message that didn't participate in a saga
  • Rule: When the message is not part of a saga, display a message indicating no saga data.​
• Feature: Detecting no Saga Data Available
  • Rule: When no saga data is available, display a message indicating the absence of data.​
    "Saga audit plugin needed to visualize saga" - "To visualize your saga, please install the appropriate nuget package in your endpoint"
• Feature: Navigation and Contextual Information
  • Rule: Provide clear navigational elements to move between views.
    A "← Back to message flow diagram" link allows users to easily navigate back to the message flow view. This is only configuring a link to the message view for now, instead of the message flow. The correct linking will be addressed in a future PR.
  • Rule: Clearly indicate contextual information like Saga ID or Saga Type.
    The saga’s type ("AuditingSaga") and unique identifier (guid) are prominently displayed at the top for reference.
• Rendering datetime values in different timezones (using the local timezone of the browser)

Implemented, but no test coverage yet:

• Display incoming messages
• Display outgoing non-timeout messages
• Display outgoing timeouts
• Message data and saga properties display fixed dummy values in this version
• Split into subcomponents