feat: PHP SDK update for version 23.1.1

[premtsd-code]

This PR updates the PHP SDK to version 23.1.1, regenerated from the Appwrite Cloud spec (cloud branch backup-migration-multitype).

What's Changed

• Fixed: Database model policies and archives now hydrate as BackupPolicy / BackupArchive instead of Index / Collection
• Added: bigint create/update APIs for legacy Databases attributes and TablesDB columns
• Added: OAuth2GooglePrompt / Prompt enums and prompt support on updateOAuth2Google
• Added: updateDenyCanonicalEmailPolicy / updateDenyDisposableEmailPolicy / updateDenyFreeEmailPolicy Project endpoints
• Updated: BuildRuntime / Runtime enums
• Updated: key-list query filters extended with key, resourceType, resourceId, secret

Why the Database fix

The Database response model previously declared policies with the Index schema and archives with the Collection schema. The server therefore serialised backup-policy/archive documents through the wrong shape — empty status strings — which broke Database::from() hydration (IndexStatus::from('') throws), aborting the Appwrite→Appwrite migration database resource report/transfer for any project that has a backup policy.

Version bump (23.1.0 → 23.1.1) and changelog included so the release is tag-ready on merge. Supersedes #69.

[greptile-apps]

Greptile Summary

This PR is a regenerated SDK bump to version 23.1.1. The headline fix corrects Database model hydration so that policies deserialises into BackupPolicy objects and archives into BackupArchive objects, rather than the wrong Index/Collection types that previously caused IndexStatus::from('') to throw and break Appwrite-to-Appwrite migration for any project with backup policies.

• Database.php fix: policies and archives now use the correct backing types, resolving the hydration crash.
• New Project endpoints: updateDenyCanonicalEmailPolicy, updateDenyDisposableEmailPolicy, and updateDenyFreeEmailPolicy added with matching tests.
• Google OAuth2 prompt: prompt parameter added to updateOAuth2Google; backed by two new enums (Prompt and OAuth2GooglePrompt) that are currently identical in values — this appears to be an artefact of the spec generator emitting separate request/response enum types.

Confidence Score: 5/5

Safe to merge — the core hydration fix is targeted and correct, and all new service methods follow established patterns.

The Database.php hydration fix directly addresses a known crash path and the change is straightforward. All new service methods match the existing OAuth2-update pattern, carry unit tests, and touch no shared state. The duplicated Prompt/OAuth2GooglePrompt enum pair is a cosmetic generator artefact that does not affect runtime correctness.

No files require special attention; OAuth2GooglePrompt.php and Prompt.php are worth a second glance to confirm the generator intent around the duplicate enum pair.

Important Files Changed

Filename	Overview
src/Appwrite/Models/Database.php	Core bug fix: policies now hydrates as BackupPolicy and archives as BackupArchive, resolving the broken hydration that caused IndexStatus::from('') to throw on any project with backup policies
src/Appwrite/Enums/OAuth2GooglePrompt.php	New enum for Google OAuth2 prompt values; functionally identical to the also-new Prompt enum — same three cases, same string values
src/Appwrite/Enums/Prompt.php	New generic Prompt enum imported by Project service and used in docs; identical in values to OAuth2GooglePrompt, leading to a duplicate-enum situation from code generation
src/Appwrite/Models/OAuth2Google.php	Added prompt field (array of OAuth2GooglePrompt); hydration and serialization follow existing patterns correctly
src/Appwrite/Services/Project.php	Added updateOAuth2Google prompt parameter and three new deny-email-policy methods; all follow established service patterns with correct HTTP methods and return types
src/Appwrite/Client.php	Version bump from 23.1.0 to 23.1.1 in user-agent, SDK version header, and package metadata
tests/Appwrite/Services/ProjectTest.php	New test methods cover updateOAuth2Google (with prompt array), and all three deny-email-policy endpoints; fixture data matches expected response shapes

_{Reviews (3): Last reviewed commit: "docs: expand 23.1.1 changelog with full ..." | Re-trigger Greptile}