Fix duplicate table device attribute updates in multi-row insert

[Caideyipi]

Summary

• Coalesce duplicate table devices in one multi-row INSERT before schema validation.
• For each (database, table, deviceId), keep the last effective non-null attribute value per attribute; missing attributes and inserted null remain no-ops.
• Add coverage for no-tag table attribute-filtered deletion and the cache-hit duplicate-device update path.

Root cause

A no-tag table is still an exact device match: its device id is the table plus an empty tag tuple. The real issue was that InsertRows validated repeated rows for the same device one by one, so multiple attribute updates in a single statement could be affected by validation/cache ordering instead of the final row state.

Tests

• mvn spotless:apply -pl iotdb-core/datanode,integration-test -P with-integration-tests
• mvn --% -o -Ddevelocity.off=true -pl iotdb-core/datanode -Dtest=TableDeviceSchemaValidatorTest test
• mvn --% -o -Ddevelocity.off=true install -DskipTests -pl iotdb-core/datanode -am
• mvn --% -o -Ddevelocity.off=true verify -DskipUTs -Dit.test=IoTDBDeletionTableIT#testDeleteDataByAttributeFilterWithoutTagColumns -DfailIfNoTests=false -Dfailsafe.failIfNoSpecifiedTests=false -pl integration-test -PTableClusterIT -P with-integration-tests

[sonarqubecloud]

Quality Gate passed

Issues
2 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud