feat: API specs update for version latest

[appwrite-specifications]

This PR contains API specification updates for version latest.

[greptile-apps]

Greptile Summary

This PR refreshes the latest OpenAPI contracts, adds a canonical combined specification, annotates security schemes with platform availability, and updates dedicated-database pricing, autoscaling, and resize-state schemas.

• Adds specs/latest/open-api3-latest.json as a combined current contract.
• Moves dedicated-database overage and add-on rates onto individual specifications.
• Adds storage-resize state fields and changes autoscaling defaults.
• Introduces one internally contradictory database example across the canonical, server, and Console artifacts.

Confidence Score: 4/5

The PR appears safe to merge after correcting the non-blocking but misleading database autoscaling example.

The contract changes are internally aligned across the latest artifacts, but the database example describes a 30 GB autoscaling ceiling for a database already at 100 GB and resizing to 120 GB.

Files Needing Attention: specs/latest/open-api3-latest-server.json, specs/latest/open-api3-latest-console.json, specs/latest/open-api3-latest.json

Important Files Changed

Filename	Overview
specs/latest/open-api3-latest-client.json	Adds client-platform metadata to shared authentication schemes without changing the client operation surface.
specs/latest/open-api3-latest-console.json	Updates dedicated-database schemas and Console authentication metadata, but repeats an incoherent autoscaling example.
specs/latest/open-api3-latest-server.json	Updates dedicated-database schemas and server authentication metadata, but sets the example autoscaling maximum below its current and target storage.
specs/latest/open-api3-latest.json	Adds the canonical combined OpenAPI contract and carries the same contradictory database storage example.

Prompt To Fix All With AI

### Issue 1
specs/latest/open-api3-latest-server.json:107067
**Autoscaling example contradicts limits**

The example enables autoscaling while reporting `storage: 100`, `storageTargetGb: 120`, and `storageAutoscalingMaxGb: 30`. Because the documented maximum is below both the current and target sizes, this cannot represent a coherent resize state and may produce misleading generated documentation or mock data. The same contradictory example appears in the Console and canonical artifacts.

---

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

_{Reviews (1): Last reviewed commit: "chore: add the canonical OpenAPI documen..." | Re-trigger Greptile}

[greptile-apps]

Autoscaling example contradicts limits

The example enables autoscaling while reporting storage: 100, storageTargetGb: 120, and storageAutoscalingMaxGb: 30. Because the documented maximum is below both the current and target sizes, this cannot represent a coherent resize state and may produce misleading generated documentation or mock data. The same contradictory example appears in the Console and canonical artifacts.

Prompt To Fix With AI

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

Comment:
**Autoscaling example contradicts limits**

The example enables autoscaling while reporting `storage: 100`, `storageTargetGb: 120`, and `storageAutoscalingMaxGb: 30`. Because the documented maximum is below both the current and target sizes, this cannot represent a coherent resize state and may produce misleading generated documentation or mock data. The same contradictory example appears in the Console and canonical artifacts.

---

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