feat: SDK update for version 29.0.0

[ChiragAgg5k]

This PR contains updates to the SDK for version 29.0.0.

What's Changed

• Stable release of the dedicated database APIs: mysql, postgresql, mongo, documentsDB, and vectorsDB services, previously released as release candidates
• Breaking: tablesDB.cutoverMigration is renamed to tablesDB.createCutover
• Breaking: Execution.functionId is replaced by resourceId and resourceType, covering function and site executions
• Added: Cloudflare, Resend, and Hugging Face OAuth providers
• Added: usageAggregateOnlyMetrics on the BillingPlan model
• Fixed: transactionId is accepted again by documentsDB and vectorsDB createDocument and createDocuments
• Updated: X-Appwrite-Response-Format is now 2.0.0
• Updated: FrameworkAdapter.fallbackFile is now optional

[greptile-apps]

Greptile Summary

This release promotes the Node SDK to 29.0.0 and aligns it with response format 2.0.0.

• Adds Cloudflare and Resend OAuth provider contracts and project configuration methods.
• Restores transaction IDs on DocumentsDB and VectorsDB create operations.
• Renames the TablesDB cutover operation and updates dedicated-database lifecycle models.
• Updates generated examples, tests, package metadata, and response models.

Confidence Score: 4/5

The dedicated database model’s nullability mismatch should be corrected before merging so consumers receive an accurate credential-generation contract.

The new shared DedicatedDatabase field is declared as always numeric despite its own API documentation stating that freshly initialized resources can return null.

Files Needing Attention: src/models.ts

Important Files Changed

Filename	Overview
src/models.ts	Adds and updates generated response contracts, but credentialGeneration excludes a documented null state.
src/services/documents-db.ts	Adds transactionId consistently across object and positional create APIs and forwards it in the request payload.
src/services/vectors-db.ts	Mirrors the DocumentsDB transaction support with aligned overload and payload mappings.
src/services/project.ts	Adds Cloudflare and Resend OAuth configuration methods with consistent routes and parameter handling.
src/services/tables-db.ts	Consistently renames the cutover method and updates its REST route across overloads, tests, and documentation.
src/services/mongo.ts	Changes credential rotation to return an asynchronous operation and documents the required polling and refetch flow.
src/services/mysql.ts	Changes credential rotation to the shared asynchronous operation contract.
src/services/postgresql.ts	Changes credential rotation to the shared asynchronous operation contract.
src/client.ts	Updates SDK identity and Appwrite response-format headers for the 29.0.0 release.

Prompt To Fix All With AI

### Issue 1
src/models.ts:8284
**Credential generation excludes null**

When a dedicated database's credential-rotation contract has not been initialized, the API contract permits `credentialGeneration` to be null, but this model declares it as an unconditional `number`, causing consumers to make unsafe numeric assumptions about the response.

```suggestion
        credentialGeneration: number | null;
```

---

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

_{Reviews (1): Last reviewed commit: "chore: update Node.js SDK to 29.0.0" | Re-trigger Greptile}

[greptile-apps]

Credential generation excludes null

When a dedicated database's credential-rotation contract has not been initialized, the API contract permits credentialGeneration to be null, but this model declares it as an unconditional number, causing consumers to make unsafe numeric assumptions about the response.

Suggested change

	credentialGeneration: number;
	credentialGeneration: number | null;

Knowledge Base Used:

• Generated models and enum vocabulary
• SDK data contracts and helpers

Prompt To Fix With AI

This is a comment left during a code review.
Path: src/models.ts
Line: 8284

Comment:
**Credential generation excludes null**

When a dedicated database's credential-rotation contract has not been initialized, the API contract permits `credentialGeneration` to be null, but this model declares it as an unconditional `number`, causing consumers to make unsafe numeric assumptions about the response.

```suggestion
        credentialGeneration: number | null;
```

**Knowledge Base Used:**
- [Generated models and enum vocabulary](https://app.greptile.com/appwrite/-/custom-context/knowledge-base/appwrite/sdk-for-node/-/docs/models-and-enums.md)
- [SDK data contracts and helpers](https://app.greptile.com/appwrite/-/custom-context/knowledge-base/appwrite/sdk-for-node/-/docs/sdk-data-contracts.md)

---

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

[loks0n]

Release PR reviewed.