feat: API specs update for version 2.3.x

[ChiragAgg5k]

Regenerated specs/2.3.x from appwrite-labs/cloud#6071 (server-ce b8ffcfd). Picks up appwrite/appwrite#13877: getColumn and getAttribute declare all 18 column and attribute models.

[greptile-apps]

Confidence Score: 4/5

The PR should not merge until the bucket size schema can represent the newly documented 5GB limit.

Findings

1.  Bucket limit exceeds integer range ▶

Fix with agent prompt

### Issue 1
specs/2.3.x/open-api3-2.3.x.json:97601
The create-bucket field now says the maximum is 5GB, but its `int32` format cannot represent more than about 2.15GB. The update-bucket field has the same mismatch. When a caller sets a bucket limit between those values, clients generated from this spec may reject it or be unable to send it.

---

For each issue above, determine whether it is valid and should be fixed. If so, fix it directly.

Summary

The 2.3.x OpenAPI spec adds eight attribute and column response variants, updates several request-field nullability declarations, and refreshes runtime choices and descriptions. The newly documented 5GB bucket limit conflicts with its int32 field format.

_{Reviews (1) · Last reviewed commit: "chore: update API specs for getColumn an..."}

[greptile-apps]

Bucket limit exceeds integer range The create-bucket field now says the maximum is 5GB, but its int32 format cannot represent more than about 2.15GB. The update-bucket field has the same mismatch. When a caller sets a bucket limit between those values, clients generated from this spec may reject it or be unable to send it.

Prompt To Fix With AI

This is a comment left during a code review.
Path: specs/2.3.x/open-api3-2.3.x.json
Line: 97601

Comment:
**Bucket limit exceeds integer range** The create-bucket field now says the maximum is 5GB, but its `int32` format cannot represent more than about 2.15GB. The update-bucket field has the same mismatch. When a caller sets a bucket limit between those values, clients generated from this spec may reject it or be unable to send it.

---

For each issue above, determine whether it is valid and should be fixed. If so, fix it directly.