feat: SDK update for version 6.1.0

[ChiragAgg5k]

This PR contains updates to the SDK for version 6.1.0.

What's Changed

• Added: Apps service for managing OAuth2 applications, keys, and installations
• Added: OAuth2 service with authorize, grant, device authorization, and consent flows
• Added: Account OAuth2 consent methods ListConsents, GetConsent, DeleteConsent, and consent token methods
• Added: app installation management methods to Organization and Teams services
• Added: installationAccessTokenDuration parameter to Project.UpdateOAuth2Server
• Added: token parameter to Sites.GetDeploymentDownload
• Added: oauth2.introspect and organization installation key scopes

[greptile-apps]

Greptile Summary

Updates the .NET SDK to version 6.1.0.

• Adds Apps, OAuth2, installation, backup, and dedicated-database APIs and models.
• Expands database models, statuses, scopes, and service operations.
• Updates generated examples, package metadata, dependencies, and publishing actions.

Confidence Score: 4/5

The PR is not yet safe to merge because several OAuth response models still destroy structured authorization details during deserialization.

OAuth consent, consent-token, grant, and token responses deserialize nested authorization details into collections and then replace those values with CLR type-name strings.

Appwrite/Models/Oauth2Consent.cs, Appwrite/Models/Oauth2ConsentToken.cs, Appwrite/Models/Oauth2Grant.cs, Appwrite/Models/Oauth2Token.cs

Important Files Changed

Filename	Overview
Appwrite/Models/Oauth2Consent.cs	Adds the OAuth consent model, but its response conversion discards structured authorization details.
Appwrite/Models/Oauth2ConsentToken.cs	Adds the consent-token model with the same lossy authorization-details conversion.
Appwrite/Models/Oauth2Grant.cs	Adds the grant model with the same lossy authorization-details conversion.
Appwrite/Models/Oauth2Token.cs	Adds the token model and coerces optional structured authorization details into an unusable string.
Appwrite/Models/AppInstallation.cs	Preserves authorizationDetails as structured response data after the earlier review feedback.
docs/examples/oauth2/approve.md	Adds an OAuth approval example as part of the generated SDK documentation.
Appwrite/Services/Oauth2.cs	Adds OAuth authorization, grant, token, consent, and revocation service methods.

Prompt To Fix All With AI

Fix the following 1 code review issue. Work through them one at a time, proposing concise fixes.

---

### Issue 1 of 1
Appwrite/Models/Oauth2Consent.cs:78
**Authorization details lose structure**

When an OAuth consent, consent-token, grant, or token response contains structured authorization details, response deserialization produces a dictionary or list and these model conversions call `ToString()` on it, causing consumers to receive a CLR collection type name instead of the authorization metadata.

_{Reviews (2): Last reviewed commit: "chore: update .NET SDK to 6.1.0" | Re-trigger Greptile}

[greptile-apps]

Named arguments do not compile

The example uses grant_id and authorization_details, but the C# method declares grantId and authorizationDetails, so copying this invocation produces compiler errors.

Prompt To Fix With AI

This is a comment left during a code review.
Path: docs/examples/oauth2/approve.md
Line: 14-15

Comment:
**Named arguments do not compile**

The example uses `grant_id` and `authorization_details`, but the C# method declares `grantId` and `authorizationDetails`, so copying this invocation produces compiler errors.

How can I resolve this? If you propose a fix, please make it concise.

[greptile-apps]

Authorization details lose structure

When an OAuth consent, consent-token, grant, or token response contains structured authorization details, response deserialization produces a dictionary or list and these model conversions call ToString() on it, causing consumers to receive a CLR collection type name instead of the authorization metadata.

Prompt To Fix With AI

This is a comment left during a code review.
Path: Appwrite/Models/Oauth2Consent.cs
Line: 78

Comment:
**Authorization details lose structure**

When an OAuth consent, consent-token, grant, or token response contains structured authorization details, response deserialization produces a dictionary or list and these model conversions call `ToString()` on it, causing consumers to receive a CLR collection type name instead of the authorization metadata.

How can I resolve this? If you propose a fix, please make it concise.