fix(sink): fix mogodb write error handling

[xxhZs]

I hereby agree to the terms of the RisingWave Labs, Inc. Contributor License Agreement.

What's changed and what's your intention?

in doc https://www.mongodb.com/zh-cn/docs/manual/reference/method/db.collection.bulkWrite/#mongodb-method-db.collection.bulkWrite
The correct error is writeErrors and writeConcernErrors
And you shouldn't use n to check if the write was successful, because there are times when n will be 0.
Let's say we delete a piece of mongodb non-existent data

Checklist

• I have written necessary rustdoc comments.
• I have added necessary unit tests and integration tests.
• I have added test labels as necessary.
• I have added fuzzing tests or opened an issue to track them.
• My PR contains breaking changes.
• My PR changes performance-critical code, so I will run (micro) benchmarks and present the results.
• My PR contains critical fixes that are necessary to be merged into the latest release.

Documentation

• My PR needs documentation updates.

Release note

[ly9chee]

And you shouldn't use n to check if the write was successful, because there are times when n will be 0.
Let's say we delete a piece of mongodb non-existent data

The initial implementation checks n > 0 becase we assumes ownership of the sinking collection. There should not be a case where n == 0, unless the user manually modified the collection.

Should we also check the ok status? Then we can expect the command is succeeded and without any write errors.
https://www.mongodb.com/docs/manual/reference/command/delete/#output

[xxhZs]

And you shouldn't use n to check if the write was successful, because there are times when n will be 0.
Let's say we delete a piece of mongodb non-existent data

The initial implementation checks n > 0 becase we assumes ownership of the sinking collection. There should not be a case where n == 0, unless the user manually modified the collection.

Should we also check the ok status? Then we can expect the command is succeeded and without any write errors. https://www.mongodb.com/docs/manual/reference/command/delete/#output

add ok, Please review if you have time, thanks!

[graphite-app]

According to the MongoDB documentation, the field name should be writeConcernErrors (plural) rather than writeConcernError. This mismatch will prevent proper error detection.

Spotted by Graphite Reviewer

Is this helpful? React 👍 or 👎 to let us know.

[ly9chee]

And you shouldn't use n to check if the write was successful, because there are times when n will be 0.
Let's say we delete a piece of mongodb non-existent data

The initial implementation checks n > 0 becase we assumes ownership of the sinking collection. There should not be a case where n == 0, unless the user manually modified the collection.
Should we also check the ok status? Then we can expect the command is succeeded and without any write errors. https://www.mongodb.com/docs/manual/reference/command/delete/#output

add ok, Please review if you have time, thanks!

LGTM!