feat: API specs update for version latest

[appwrite-specifications]

This PR contains API specification updates for version latest.

[greptile-apps]

Confidence Score: 4/5

The PR should not merge until the update-bucket compression contract handles null consistently.

Findings

1.  Conflicting compression constraints ▶

Fix with agent prompt

### Issue 1
specs/latest/open-api3-latest.json:97982
On `PUT /storage/buckets/{bucketId}`, the schema now allows `compression` to be null, but its three alternatives accept only the strings `none`, `gzip`, and `zstd`. A request with `"compression": null` is therefore permitted by one part of the contract and rejected by another, causing schema validation to fail.

---

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

Summary

The PR updates the moving OpenAPI contract with nullable request fields, additional attribute and column response variants, an installation URL field, and impersonation documentation.

• The update-bucket schema has a contradictory nullable compression constraint.

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

[greptile-apps]

Conflicting compression constraints On PUT /storage/buckets/{bucketId}, the schema now allows compression to be null, but its three alternatives accept only the strings none, gzip, and zstd. A request with "compression": null is therefore permitted by one part of the contract and rejected by another, causing schema validation to fail.

Knowledge Base Used: Published API contract artifacts

Prompt To Fix With AI

This is a comment left during a code review.
Path: specs/latest/open-api3-latest.json
Line: 97982

Comment:
**Conflicting compression constraints** On `PUT /storage/buckets/{bucketId}`, the schema now allows `compression` to be null, but its three alternatives accept only the strings `none`, `gzip`, and `zstd`. A request with `"compression": null` is therefore permitted by one part of the contract and rejected by another, causing schema validation to fail.

**Knowledge Base Used:** [Published API contract artifacts](https://app.greptile.com/appwrite/-/custom-context/knowledge-base/appwrite/specs/-/docs/api-contract-artifacts.md)

---

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