feat: API specs update for version 2.0.x

[appwrite-specifications]

Summary

Generated from Cloud main at eb0067830ee748f4151ca1f0f1ed441339f456d1 using the specs workflow with version=2.0.x and push=true, as approved for CLO-4377.

Verification

• Workflow run passed, including the specs push/PR step. The 2.0.x run also generated SDK examples.
• Downloaded the generated artifact and checked that all six compound schemas exactly match the previously reviewed Cloud dry-run schemas: two 10-member response unions and four 18-member item unions. No compound x-mapping remains.
• Artifact SHA-256: d0e19b23689a86c92887f8700a467ae1d9df56b0697721ce34aec706df3fa323.
• Producer: 5f07aa7182958f263aef68fff928f5ed4b78a5a1; SDK generator 5.0.0; OpenAPI 0.2.4.

The main-branch artifact differs from the earlier dry run outside those six compound sites; this is not a claim of whole-document parity. See Cloud integration and prior validation limitations. Full-document validation and deployed consumer behavior against these new documents are not established by this workflow. Canonical publication requires merging this PR.

[greptile-apps]

Confidence Score: 4/5

The PR should not merge until the newly added OpenAPI security alternatives are reconciled with the affected operations' declared platform authentication requirements.

Findings

1.  Security Alternative Omits Credential ▶

Fix with agent prompt

### Issue 1
specs/2.0.x/open-api3-2.0.x.json:65037-65039
The new `{"Project": []}` entry is a complete OpenAPI authentication alternative, but this Console-only invoice-download operation declares both `Project` and `ImpersonateUserId` in `x-appwrite.auth`. Standard OpenAPI clients and documentation can therefore send a project-only request that fails authorization. The same mismatch affects invoice viewing, function deployment downloads, and avatar operations.

---

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

Summary

• Adds Kakao and TikTok OAuth provider operations, models, enums, and SDK examples.
• Standardizes compound response schemas and object defaults.
• Corrects generated Swift/Apple collection literals and Rust void-delete examples.
• Adds JSON response headers to REST examples and refreshes DNS examples.
• One group of newly added OpenAPI security alternatives conflicts with the corresponding platform-specific authentication metadata.

_{Reviews (1) · Last reviewed commit: "chore: publish standard compound OpenAPI..."}