Add support for updateOption parameter in string editing endpoints

The Crowdin API adds a new optional `updateOption` query parameter to the source string editing endpoints: **Edit String** (`PATCH /projects/{projectId}/strings/{stringId}`) and **String Batch Operations** (`PATCH /projects/{projectId}/strings`).

The parameter defines whether existing translations and approvals are kept when a string is updated, and is applied only when `text` or `identifier` is changed. Allowed values:

- `keep_translations_and_approvals` (default)
- `keep_translations`
- `clear_translations_and_approvals`

API client libraries should be updated to expose `updateOption` on these endpoints so consumers can control translation/approval retention when editing strings via the SDK.

**References:**
- [Edit String](https://support.crowdin.com/developer/api/v2/#operation/api.projects.strings.patch)
- [String Batch Operations](https://support.crowdin.com/developer/api/v2/#operation/api.projects.strings.batchPatch)

Start by locating the Go client entry points for the Edit String and String Batch Operations endpoints. Compare their request parameters with the Crowdin API references linked in the issue, then verify that updateOption is exposed for both endpoints with the documented default and allowed values. Done means consumers can control translation and approval retention through the SDK.

Written by the indexing model from the issue text.