Prompt dataverse events

Act as an event-driven architecture expert and architect. Create a comprehensive MkDocs documentation page that addresses the challenge of transforming generic DataVerse CRUD events into specific business events using a containerized .NET application.

Requirements: - Focus specifically on DataVerse Contact entities as the primary example - Explain how DataVerse publishes events through Service Endpoints (include an abstract section for those unfamiliar with DataVerse mechanics) - Document the architecture where events flow from DataVerse → Azure Event Hub → Containerized .NET Application (running in AKS/Container App Environment) → Another Event Hub for business events - Address two key scenarios: 1. Generic contact update events for systems that need to project changes into custom views 2. Specific business events when a Contact's email address changes - Show how to detect specific field updates using pre/post images in Updated events - Include Mermaid diagrams to illustrate the architecture and event flow - Provide C# code snippets focusing on the important aspects (not complete applications) - Use text-only format suitable for MkDocs - Make the solution concrete and practical for implementation - Discuss how to handle the "at-least-once"-delivery paradigm in Event Hub - Recommend important metrics to monitor in the solution - can be done with pseudo code and an explanation of why the metric is important.

Key Technical Focus Areas: - Event translation patterns in C# - Working with DataVerse pre/post images - Field-level change detection - Business event schema design - Containerized application architecture for event processing

The documentation should serve as a comprehensive guide for developers implementing this event-driven pattern with DataVerse and Azure Event Hub. You have finished the task, when I can download a markdown file to be used by MkDocs