feat: SDK update for version 17.0.0

[ChiragAgg5k]

This PR contains updates to the SDK for version 17.0.0.

What's Changed

• Breaking: SDK now targets Appwrite 2.2 (X-Appwrite-Response-Format: 2.2.0)
• Breaking: removed Account.listLogs, Teams.listLogs, Users.listLogs and the Log, LogList models
• Breaking: removed Client.setDevKey, the Projects dev key methods, and the DevKey, DevKeyList models
• Breaking: removed Project.getUsage, the ProjectUsageRange enum and UsageProject, MetricBreakdown models
• Breaking: removed Organizations.cancelDowngrade
• Breaking: Manager.listBlocks returns ManagerBlockList; BlockList, BlockDelete renamed to ManagerBlockList, ManagerBlockDelete with a new ManagerBlock model
• Breaking: Block model dropped billingPlan, organizationId, organizationName, projectName, region, reason
• Breaking: Project.devKeys field removed
• Breaking: BillingPlanGroup.Starter replaced by Free and Start
• Breaking: OrganizationKeyScopes dev key and organization.keys.* scopes replaced by organization.projects.keys.*
• Breaking: CacheDatabase.Logs and QuerySuggestionResource DevKeys, Executions, Stats values removed
• Added: Organization project key methods listProjectKeys, createProjectKey, createEphemeralProjectKey, getProjectKey, updateProjectKey, deleteProjectKey
• Added: Account.createIdTokenSession for native Apple and Google sign-in with IdTokenProvider enum
• Added: Account.createEmailVerificationOTP and Account.updateEmailVerificationOTP
• Added: Messaging.createAppwriteProvider and Messaging.updateAppwriteProvider for Appwrite push, with qos and expiry on Topic
• Added: Organizations.getEstimation for the current billing cycle charge estimate
• Added: Project.updatePasswordPwnedPolicy with PolicyPasswordPwned model and ProjectPolicyId.Passwordpwned
• Added: nativeEnabled, nativeClientIds parameters on Project.updateOAuth2Apple and Project.updateOAuth2Google and matching fields on OAuth2Apple, OAuth2Google
• Added: Framework.Jaspr, ProjectEmailTemplateId.OtpVerification, ProjectKeyScopes.DedicatedDatabasesExecute, QuerySuggestionResource.AppwritePushLedger
• Added: passwordPwned on User, providerIdToken on Identity, firstAccessedAt and mcpAccessedAt on Project, eligibleCountries on BillingPlan
• Added: protocol, accept, acceptLanguage, queryKeys fields on UsageDataPoint
• Fixed: empty-string required path parameters are rejected instead of sent to the API

[greptile-apps]

Confidence Score: 5/5

The PR appears safe to merge; the only outstanding concern is non-blocking outdated server-version guidance already tracked in the existing README thread.

Findings

1.  Server target remains outdated ▶

Fix with agent prompt

### Issue 1
README.md:undefined-9
This still says the SDK targets Appwrite 2.0.x, while the updated badge and client response-format header target 2.2.0. That conflicting compatibility guidance can lead users to select an incompatible server or SDK version.

```suggestion
**This SDK targets Appwrite server version 2.2.x as shipped on Appwrite Cloud.** Self-hosted releases can lag behind Cloud - if you run an older self-hosted build, use a matching older SDK from [previous releases](https://github.com/appwrite/sdk-for-console/releases) when APIs differ.
```

Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!

---

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

Summary

Updates the Console SDK for Appwrite 2.2 and releases version 17.0.0.

• Adds new authentication, project-key, messaging, billing-estimation, and password-policy APIs.
• Updates models, enums, generated examples, request validation, and the response-format target.
• Removes obsolete logs, dev-key, project-usage, and downgrade APIs.
• Clarifies that the empty-string validation change applies only to required path parameters.

_{Reviews (2) · Last reviewed commit: "docs: scope the empty-string check to pa..."}

[greptile-apps]

Server target remains outdated

This still says the SDK targets Appwrite 2.0.x, while the updated badge and client response-format header target 2.2.0. That conflicting compatibility guidance can lead users to select an incompatible server or SDK version.

Suggested change

	**This SDK targets Appwrite server version 2.0.x as shipped on Appwrite Cloud.** Self-hosted releases can lag behind Cloud — if you run an older self-hosted build, use a matching older SDK from [previous releases](https://github.com/appwrite/sdk-for-console/releases) when APIs differ.
	**This SDK targets Appwrite server version 2.2.x as shipped on Appwrite Cloud.** Self-hosted releases can lag behind Cloud — if you run an older self-hosted build, use a matching older SDK from [previous releases](https://github.com/appwrite/sdk-for-console/releases) when APIs differ.

Knowledge Base Used: Client configuration and HTTP transport

Prompt To Fix With AI

This is a comment left during a code review.
Path: README.md
Line: 9

Comment:
**Server target remains outdated**

This still says the SDK targets Appwrite 2.0.x, while the updated badge and client response-format header target 2.2.0. That conflicting compatibility guidance can lead users to select an incompatible server or SDK version.

```suggestion
**This SDK targets Appwrite server version 2.2.x as shipped on Appwrite Cloud.** Self-hosted releases can lag behind Cloud — if you run an older self-hosted build, use a matching older SDK from [previous releases](https://github.com/appwrite/sdk-for-console/releases) when APIs differ.
```

**Knowledge Base Used:** [Client configuration and HTTP transport](https://app.greptile.com/appwrite/-/custom-context/knowledge-base/appwrite/sdk-for-console/-/docs/sdk-client-and-transport.md)

---

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

Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!