Remove required `version` field from project expiry/lock response schemas
BreakingBreaking change
This is a breaking change — integrations that rely on the affected behaviour will need updates before the change rolls out.
What changed
The version field has been removed from two response object schemas — the scheduled-expiry object (previously required alongside expiresAt) and the locked object (previously required alongside lockedAt and lockedBy) — across 6 endpoint definitions. Clients that read and depend on version (e.g. to track ExpireProject event versioning or to seed a re-schedule counter) will no longer receive it, which is a breaking change for those integrations.