Enhance SyncConnectionRequest with full rebuild and since date support

[jfrench9]

Summary

This PR enhances the event-driven ingestion pipeline by extending the SyncConnectionRequest model with new attributes (full_rebuild and since_date) and updating the op_update_event_block operation to leverage these capabilities. These changes enable more flexible control over synchronization behavior, allowing callers to request full data rebuilds or incremental syncs from a specific date.

Key Accomplishments

• Extended SyncConnectionRequest model: Added full_rebuild (boolean) and since_date (date/datetime) attributes to the sync connection request, providing granular control over sync operations.
• Updated op_update_event_block: Enhanced the event block update operation to accommodate the new request attributes, ensuring the API layer properly handles full rebuild and date-based sync scenarios.
• Expanded serialization/deserialization logic: The model now correctly handles the new fields throughout the request lifecycle (construction, validation, serialization to dict/JSON, and deserialization).

Breaking Changes

• The SyncConnectionRequest model signature has been extended. Existing consumers that instantiate the model via positional arguments or perform strict schema validation may need to be updated to account for the new optional fields. However, since these are additive attributes, backward compatibility should be maintained for most standard usage patterns.

Testing Notes

• Verify that SyncConnectionRequest can be instantiated with and without the new full_rebuild and since_date attributes (ensure backward compatibility with existing call sites).
• Test that full_rebuild=True triggers the expected full data rebuild behavior end-to-end through the event block update operation.
• Test that providing a since_date correctly scopes the sync to only process data from the specified date onward.
• Validate proper serialization/deserialization of the new fields (JSON round-trip, dict conversion).
• Confirm that omitting both new fields preserves the existing default sync behavior.

Infrastructure Considerations

• No new dependencies or infrastructure changes are required.
• Downstream services and consumers of the RoboSystems client SDK should be reviewed to ensure compatibility with the updated model, particularly any schema validators or contract tests.
• API documentation should be updated to reflect the new optional parameters available on sync connection requests.

---

🤖 Generated with Claude Code

Branch Info:

• Source: feature/event-driven-ingest
• Target: main
• Type: feature

Co-Authored-By: Claude noreply@anthropic.com