Generate SDK for v3.2.0

[mridang]

Description

This pull request contains a new, auto-generated version of the SDK.

The code in this PR was generated by our internal script based on the latest Protocol Buffers (protobuf) definitions from the upstream zitadel/zitadel repository. No manual changes have been made.

Related Issue

N/A. This PR is part of the automated process to keep the SDK synchronized with upstream releases. An issue is not typically created for these routine updates.

Motivation and Context

This change is required to ensure the SDK is up-to-date with the latest version of the ZITADEL API.

This allows developers to access the newest features, bug fixes, and performance improvements exposed by the platform, ensuring client-side parity with the server.

The source of truth for all API changes is the official ZITADEL changelog, which can be found by referencing the version in the title of this pull request.

➡️ View ZITADEL Releases on GitHub

How Has This Been Tested?

The changes have been tested through the following automated steps:

• SDK Generation: The generation script completed successfully without errors.
• Linters and Formatters: The generated code passes all repository linting and formatting checks.
• Continuous Integration (CI): The standard CI pipeline for this repository has been triggered to run builds, and if applicable, execute any auto-generated test suites. All checks must pass before this PR can be merged.

Documentation:

The primary documentation for the API changes resides in the upstream ZITADEL release notes.

Any relevant SDK-specific documentation (such as README.md or method-level comments) has been automatically updated by the generation script as part of this pull request.

Checklist:

• I have updated the documentation accordingly. (Automated: Generator updates code-level documentation)
• I have assigned the correct milestone or created one if non-existent.
• I have correctly labeled this pull request. (Automated: 'sdk-generation', 'enhancement' labels applied)
• I have linked the corresponding issue in this description. (Automated: N/A as per the "Related Issue" section)
• I have requested a review from at least 2 reviewers.
• I have checked the base branch of this pull request. (Automated: PR is targeted at the 'main' or 'develop' branch)
• I have checked my code for any possible security vulnerabilities. (Automated: Generation is from a trusted upstream source; CI may include security scans)