feat: regenerate API client from OpenAPI spec

[convoy-sdk-bot]

Automated regeneration via openapi-python-client from docs/v3/openapi3.yaml on frain-dev/convoy main. Hand-written webhook verify (src/convoy/utils/) is untouched by the sync script.

---

Note

Medium Risk
Breaking type change on create-event 201 data for SDK users who relied on ModelsEventResponse or stub fields; runtime parsing is stricter and omits fields no longer in the queued response.

Overview
Regenerated client models align create-event HTTP 201 bodies with the updated OpenAPI spec: successful creates now deserialize data as ModelsEventQueuedResponse (event_type, idempotency_key, uid as event id) instead of full ModelsEventResponse (broadcast) or HandlersStubType0 (dynamic, endpoint, fanout).

Broadcast, dynamic, endpoint, and fanout create helpers pick up matching docstring notes that uid is in the 201 body and that GET /events/{eventID} or GET /eventdeliveries?eventId= can track delivery.

Callers that assumed a full event object on create may need to use uid and fetch the event separately; code already reading result.data.uid stays compatible.

^{Reviewed by Cursor Bugbot for commit e32f6e1. Bugbot is set up for automated code reviews on this repo. Configure here.}

[convoy-sdk-reviewer]

SDK reviewer app: approving a generated-paths-only diff on the regen branch. Auto-merge completes only after required status checks pass.