Fix Kafka patch filter precondition handling

[Arnab Nandy (arnabnandy7)]

Description

Fixes #49944.

Updates the Cosmos DB Kafka sink connector so ItemPatch writes treat 412 Precondition Failed responses as successful no-op skips when a non-empty azure.cosmos.sink.write.patch.filter predicate is configured.

The change applies consistently to both bulk and point-write paths. Patch operations without a filter continue to treat 412 responses as failures. Inline comments document that this behavior should be revisited if etag/If-Match support is added to patch operations.

The existing Kafka sink patch integration test now covers conditional patch replay for both bulk and point writers. The configuration reference and CHANGELOG have also been updated.

All SDK Contribution checklist:

• The pull request does not introduce [breaking changes]
• CHANGELOG is updated for new features, bug fixes or other significant changes.
• I have read the contribution guidelines.

General Guidelines and Best Practices

• Title of the pull request is clear and informative.
• There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For more information on cleaning up the commits in your PR, see this page.

Testing Guidelines

• Pull request includes test coverage for the included changes.

[azure-pipelines]

Azure Pipelines:
Successfully started running 2 pipeline(s).
33 pipeline(s) were filtered out due to trigger conditions.
There may be pipelines that require an authorized user to comment /azp run to run.

[Copilot]

Copilot encountered an error and was unable to review this pull request. You can try again by re-requesting a review.

Note

This error may be related to your runner configuration. You can now configure runners for Copilot code review separately from Copilot cloud agent by creating a copilot-code-review.yml file with your setup steps. Read the docs for details.

[Copilot]

Copilot encountered an error and was unable to review this pull request. You can try again by re-requesting a review.

Note

This error may be related to your runner configuration. You can now configure runners for Copilot code review separately from Copilot cloud agent by creating a copilot-code-review.yml file with your setup steps. Read the docs for details.

[github-actions]

Thank you for your contribution Arnab Nandy (@arnabnandy7)! We will review the pull request and get back to you soon.

[Copilot]

Pull request overview

Copilot reviewed 5 out of 5 changed files in this pull request and generated no new comments.