docs: add event-driven status history integration proposal

[gurveenbagga]

Overview

This PR proposes a standardized, event-driven integration architecture for Moqui with external ERP systems like Dynamics 365 and NetSuite.

Key Changes

• Immutable Event Detection: Shifted from monitoring header entities (e.g., OrderHeader) to monitoring status history entities (OrderStatus, ShipmentStatus, ReturnStatus).
• One-time Triggering: Leveraging history records ensures that integration events are triggered exactly once per state transition.
• Decoupled Architecture: Proposed a separate DataFeed per integration event for isolation and independent scaling.
• Detailed XML Examples: Provided DataDocument and DataFeed snippets for SalesOrderCreated, SalesOrderCancelled, SalesOrderFulfillment, and SalesOrderReturnCompleted events.

Impact

• Eliminates redundant integration triggers.
• Provides a clean "Outbox" pattern audit trail via Moqui's native data feed framework.
• Reduces performance impact on online transactions by utilizing asynchronous push.