feat: API specs update for version latest

[appwrite-specifications]

This PR contains API specification updates for version latest.

[greptile-apps]

Confidence Score: 5/5

The PR appears safe to merge; the previously unsupported ID-token provider values have been removed and no new actionable issue was found.

Findings

1.  Unsupported Providers Advertised ▶

Fix with agent prompt

### Issue 1
specs/latest/open-api3-latest.json:4622-4628
The new ID-token session endpoint says it supports only Apple and Google, but its request schema allows the full OAuth provider set and uses `amazon` as the example. Generated clients and schema-based tools will treat unsupported providers as valid, causing callers to send requests that the API rejects. Restrict the schema and example to Apple and Google.

---

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

Summary

Updates the latest Appwrite OpenAPI specification from version 2.0.0 to 2.2.0.

• Adds ID-token sessions and email-verification OTP endpoints.
• Updates endpoint metadata, schemas, permissions, models, and examples.
• Restricts ID-token session providers to the documented Apple and Google options, resolving the previous review finding.

_{Reviews (2) · Last reviewed commit: "chore: state the project path binding as..."}

[greptile-apps]

Unsupported Providers Advertised

The new ID-token session endpoint says it supports only Apple and Google, but its request schema allows the full OAuth provider set and uses amazon as the example. Generated clients and schema-based tools will treat unsupported providers as valid, causing callers to send requests that the API rejects. Restrict the schema and example to Apple and Google.

Prompt To Fix With AI

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

Comment:
**Unsupported Providers Advertised**

The new ID-token session endpoint says it supports only Apple and Google, but its request schema allows the full OAuth provider set and uses `amazon` as the example. Generated clients and schema-based tools will treat unsupported providers as valid, causing callers to send requests that the API rejects. Restrict the schema and example to Apple and Google.

---

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