feat(sink): support es sink partial update

[xxhZs]

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

What's changed and what's your intention?

We will send all the columns every time we update, which will cause the load of es to become high, after this pr, es sink will judge the columns of update, and only send the modified columns

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

[hzxa21]

I think this map is unnecessary because UpdateDelete and UpdateInsert must be adjacent to each other so we only need to cache one row for the check.

[hzxa21]

It is more efficient to populate the new col_indices proactively instead of calling retain on the full list for each column. Example:

if let Some(insert_column) = insert_column
        && let Some(delete_column) = delete_column
        && insert_column == delete_column {
  // do nothing
} else {
  modified_col_indices.push_back(index);
}