Implement RESO EntityEvent change-feed replication using the RCP-027 sequence number protocol

Verified steps

1. Confirm the MLS server supports the EntityEvent resource by querying the RESO service document ($metadata) and verifying that EntityEvent is listed as an available entity set
2. Perform an initial full-load by paginating through the target resource (e.g., Property) using $top and $skip or server-side pagination tokens to capture the full baseline dataset and record the maximum ModificationTimestamp or sequence number seen
3. Begin incremental replication by querying the EntityEvent resource with a filter on EventTimestamp greater than the last processed sequence number; each EntityEvent record references the ResourceName, KeyValue, and EventType (Add, Modify, Delete)
4. For each EntityEvent with EventType Add or Modify, fetch the current record from the target resource endpoint using the referenced KeyValue to retrieve the full updated payload
5. For EventType Delete events, remove the corresponding record from the local data store using the KeyValue; do not attempt to fetch the deleted record from the source as it will return a 404 or 410
6. Persist the highest processed EventTimestamp or sequence number in durable storage after each successful replication cycle to enable accurate resumption after failure or downtime