…table (apache#35917)

close apache#34551

Problem: As shown in the issue above, if a key deleted by a delete
statement is written to by updating only certain columns, the data will
not display correctly.

Reason: The delete statement deletes the data by writing a delete
predicate, which is stored in the rowset meta and applied during data
retrieval to filter the data. However, partial column updates do not
consider the effect of the delete predicate when reading the original
data. The imported key should be considered as a new key (since it has
already been deleted), but it is actually treated as an old key.
Therefore, only some columns are updated, leading to incorrect results.

Solution: Consider the delete predicate during partial column updates,
but this method will result in reading more columns, as shown in apache#35766.
Thus, in this PR, we change the delete operation in the mow table from
writing a delete predicate to writing a delete sign, which effectively
resolves the issue.

…d mode (apache#37151)

Problem: The `test_new_partial_update` case fails to run in cloud mode,
but it passes in local mode.

Reason: In PR apache#35917, we introduced a new table attribute
`enable_light_delete`. When executing schema changes with `alter table
set xxx` statements, the local and cloud modes process the logic
differently. The cloud mode has its unique processing logic, which was
not addressed in the mentioned PR, leading to failures in the cloud
environment.

Solution: To resolve the issue, we need to complete the missing schema
change logic for the cloud mode. Once this is implemented, the problem
should be resolved.