Add event action types and integrate into event block models

[jfrench9]

Summary

Introduces event_action_type support across the event block model layer in the robosystems_client. This change adds new type definitions and integrates them into the create, update, and envelope models for event blocks.

Key Accomplishments

• New type models: Added three new event_action_type_0 model classes for CreateEventBlockRequest, UpdateEventBlockRequest, and EventBlockEnvelope, providing structured type definitions for event actions.
• Model integration: Updated existing CreateEventBlockRequest, UpdateEventBlockRequest, and EventBlockEnvelope models to incorporate the new event_action_type field, enabling event blocks to carry action type metadata.
• Module exports: Updated models/__init__.py to export all new model classes, ensuring they are accessible throughout the client library.

Changes Breakdown

Area	Change
CreateEventBlockRequest	Added event_action_type field + new type model
UpdateEventBlockRequest	Added event_action_type field + new type model
EventBlockEnvelope	Added event_action_type field + new type model
models/__init__.py	Registered new model exports

Breaking Changes

• Potentially breaking for consumers: If any downstream code performs strict schema validation or exhaustive field checks on CreateEventBlockRequest, UpdateEventBlockRequest, or EventBlockEnvelope, the addition of the new event_action_type field may require updates. However, since the field is additive, most standard usage patterns should remain unaffected.

Testing Notes

• Verify that event block creation, update, and retrieval flows correctly serialize and deserialize the new event_action_type field.
• Confirm that the new type models (*_event_action_type_0) properly handle expected values and edge cases (e.g., None/Unset states).
• Validate backward compatibility — existing event blocks without an event_action_type should continue to work without errors.

Infrastructure Considerations

• This is a client-side model change; ensure that the corresponding API/backend already supports the event_action_type field before deploying consumers that depend on it.
• Auto-generated client code (if applicable) should be kept in sync with the upstream API schema to avoid drift.

---

🤖 Generated with Claude Code

Branch Info:

• Source: feature/add-event-action
• Target: main
• Type: feature

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